Upgrade internal self-hosted Sentry infrastructure to version 22+

We evaluated migration to a hosted sentry setup, which was not feasible to move forward - https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/13963 - so the target is now to define a clear path forward for our current self-hosted setup and how to transform it so we have the latest version (atm 22.2.0) running.

Documentation: https://develop.sentry.dev/self-hosted/ Repo: https://github.com/getsentry/self-hosted

Suggested Approaches

I currently see 2 different approaches that I would like to hear everyone's input (and of course also if there are any others?).

Upgrade the current instance

Classic way of upgrading, but that would need also at least one hop in between (we need to check if even more), also an OS upgrade is needed (https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/15030).

Switch over

Maybe it would be way easier to setup Sentry completely new on complete new instances (maybe Kubernetes - https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/9118 ?), import exported users + settings and then switch gitlab.com to report to the complete new infrastructure

ToDo

• Explore different approaches
• Weigh and estimate the work needed