Matomo on Kubernetes with Rolling Deployments

I am currently trying to deploy Matomo to a Kubernetes cluster, but I’m running into some issues with the database updates when activating plugins or upgrading the Matomo version. The migrations aren’t backwards compatible, making it infeasible to do zero-downtime deployments with rolling updates, immutable deployments or canary deployments.

Is there a guideline or a previous experience of integrating these migrations in a CI/CD pipeline? I imagine the migrations would have to be adapted to be backwards compatible and the solution would apply to vanilla load balanced environments as well.

1 Like