Hi, first of all, thanks for the amazing product that is Sentry, we have been using the 9.1.2 self-hosted version on our Swarm cluster for a while now and it’s been very helpful to improve the way we detect and handle errors!
I wanted to tackle the upgrade to v10 today, but was a bit thrown off by the new way of doing things. Am I right thinking that using the
install.sh script would only ever work if it ran from the machine the current Sentry instance is running on, with it being already deployed only with docker-compose and nothing else?
If that’s the case, I reckon I’m not the first and won’t be the last to wonder how to install and upgrade Sentry v10 on a Swarm or k8s cluster. I initially thought I’d be able to just build my image with our custom configs in a GitLab-CI pipeline, and then simply update the image on our cluster, letting Sentry do the rest when it comes to migrations and all other stuff (like what GitLab is doing in its Omnibus package for instance), but I guess I was mistaken?
Nonetheless, Sentry really is a good product, and we are more than happy to tackle things a bit more manually to make it work. It seems a few unofficial Heml charts have already been published, but we are actually looking for a solution for a Swarm stack. Moreover, it would be great if we were able to migrate our existing 9.1.2 instance without losing any data or configuration.
Is someone willing to help a bit with this task? This topic could probably be helpful for others who are facing the same issue. Even just a global overview of the workflow we should implement, like steps to run from CI, how to deploy, handle migrations and so on, would be tremendously helpful.