🌇 Sunsetting Kubernetes Deployments
This page covers our PostHog Kubernetes deployment, which we are currently in the process of sunsetting. Existing customers will receive support until May 31, 2023 and we will continue to provide security updates for the next year.
For existing customers
We highly recommend migrating to PostHog Cloud (US or EU). Take a look at this guide for more information on the migration process.Looking to continue self-hosting?
We still maintain our Open-source Docker Compose deployment. Instructions for deploying can be found here.
We want to make sure upgrading PostHog is as smooth as possible. We use a synchronous and an asynchronous migration framework to make sure database migrations are easy to be deployed, rolled back and safe to run.
Because some data migrations require touching tables that can get very large for some PostHog installation, some migrations are a little more involved.
For more information on any extra steps needed when updating to specific versions, check out our upgrade notes.
If you need help, feel free to join our community Slack for further assistance.
1. Get and update the Helm repo
To upgrade the Helm release posthog in the posthog namespace:
2. Follow the upgrade notes
Take note of the numbers of the Helm chart version (in the format posthog-{major}.{minor}.{patch} - for example, posthog-19.15.1) when running the commands above.
Make sure to check the upgrade notes for the new version, along with all the prior versions before moving forward**.
3. Run the upgrade
Check the Helm documentation for more info about the helm upgrade command.