Remix clone Hacker News

This absolutely mirrors my experience. Sentry was straightforward to deploy years ago, but now seems like one of the more egregious offenders in the, 'self host-able but increasingly prohibitively complex by design' category.

As others have said, we've [0] found the only practical way to deploy this for our clients is Kuberentes + Helm chart, and that's on bare-metal servers (mostly Hetzner). It runs well if you can throw hardware and engineering time at it, which thankfully we can. But given the option we would love a simpler solution.

[0]: https://lithus.eu

▲

wg0 2 days ago | parent [-]

And how do you install and maintain/upgrade kubernetes? Are you running databases also on kubernetes?

▲

adamcharnock 2 days ago | parent [-]

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...

▲

apexalpha a day ago | parent | next [-]

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.

▲

baq a day ago | parent | prev [-]

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

	▲	adamcharnock a day ago \| parent [-]
		Yes, you could definitely do that. Although if going that route I'd consider taking a run at their docker compose self-hosting instructions first.