Very slow migration (2.61.0 --> 3.3.0)
Hi team!
First of all, thank you for this amazing piece of software! Really great dev experience so far.
We are self-hosting Zitadel on Kubernetes. As we continue developing our application that will eventually integrate with Zitadel, we decide to update our dependencies, including Zitadel itself. We upgraded from 2.61.0 to 3.3.0. The database contains ~84,000 users.
Our Kubernetes deployment uses hooks to ensure that
Instead, we wiped the database and re-imported, which is only an option in the dev environment. I would like to improve this process in the future. Is a very slow migration expected? What are best practices to ensure a swift update?
Thanks!!
First of all, thank you for this amazing piece of software! Really great dev experience so far.
We are self-hosting Zitadel on Kubernetes. As we continue developing our application that will eventually integrate with Zitadel, we decide to update our dependencies, including Zitadel itself. We upgraded from 2.61.0 to 3.3.0. The database contains ~84,000 users.
Our Kubernetes deployment uses hooks to ensure that
zitadel-setup runs ahead of new deployment. However, we've been having an issue with the job timing out. It currently has a timeout of, 9000s but still doesn't fully complete the migration successfully. It seemingly gets stuck at the user table migration.Instead, we wiped the database and re-imported, which is only an option in the dev environment. I would like to improve this process in the future. Is a very slow migration expected? What are best practices to ensure a swift update?
Thanks!!
