Upgrade Zitadel from v2.37.3 to latest
Hey
So I'm trying to upgrade zitadel from v2.37.3 to the latest version.
Unfortunately Zitadel hasn't been upgraded regularly so we are gonna need this jump.
Question is how can I achieve it without any database issues whatsoever
I am using docker and a docker compose file any help can be appreciated.
7 Replies
Hi @Perditus, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.
Answer
I wasn't able to find a direct answer about upgrading from v2.37.3 to the latest version, here are some relevant sources:
1. Set up Zitadel with Docker Compose ](https://zitadel.com/docs/self-hosting/deploy/compose) ) : This provides the current Docker Compose setup configuration but doesn't cover version upgrade procedures.
2. Mirror data from cockroach to postgres ](https://zitadel.com/docs/self-hosting/manage/cli/mirror) ) : This covers database migration functionality that could be relevant for ensuring data safety during upgrades.
If you'd like me to click the "Ask for help" button to tag a team member who can provide specific guidance on upgrading from v2.37.3, let me know!
To learn more, see the sources I considered:
[1] Set up Zitadel with Docker Compose
[2] Mirror data from cockroach to postgres
Feel free to tag @Ask Inkeep with additional questions.
Got it. Tagging @Rajat for additional help.
Any possibilities?
hey @Perditus apologies for the delay, but this is a huge upgrade from v2.37.3, I have to check with the team, meanwhile you can tell me more about it(users/cloud OR selfhosted/ db versions/tech stack)
Hey!
It is self hosted using docker compose and also we have LDAP connected.
About 160 users have been connected with around 10 apps connected
Db version is PostgresSQL 16.3
okay I will check with my team about it. Thanks
Also one of the main reasons why we want to switch cus there is a weird 180%+ CPU usage on the zitadel DB and about 50% on the zitadel main instance
Has there been any news?
hey @Perditus so I read a bit more and this could be done in 3 steps. I am using this as reference
1. backup your DB.
2. Read this advisory for any breaking changes. any zitadel version ≥
2.44.0 needs the new flag --init-projections if you want the migration to finish before the runtime starts
3.When it says “setup successful”, start the normal ZITADEL container.
this should be it 🙂