In our case we have a collection of Ansible roles we use for the purpose. We run databases using the Stackgres operator either using logical replication on local fast NVMe dives, on top of OpenEBS/Mayastor replicated block-storage.

But we specialise in this so that our clients don't have to. As much as I do actually love Kubernetes, the fact that the _easiest_ way to self-host Sentry is via Kubernetes is not a good sign. And choosing to spin up a Kubernetes cluster just to run Sentry would feel a lot like the lady who swallowed a fly[0].

[0]: https://en.wikipedia.org/wiki/There_Was_an_Old_Lady_Who_Swal...

Thanks for the poem, it seems pretty apt for IT in 2025.

That said I would honestly prefer if the industry would just settle on K8s as our OS.

I really do not see any benefit that sentry could bring on its own compared to a solid set of Helm charts for k8s.

Does it really have to be a proper cluster, though? Can it be e.g. a single node k3s?