Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Official Helm charts for Synapse and Element #33

Open
outofrange opened this issue Feb 7, 2024 · 2 comments
Open

Official Helm charts for Synapse and Element #33

outofrange opened this issue Feb 7, 2024 · 2 comments

Comments

@outofrange
Copy link

outofrange commented Feb 7, 2024

Is your feature request related to a problem? Please describe.
I'd like to use an official Helm chart for homeservers running in Kubernetes environments.

Describe the solution you'd like
We are running our homeserver in Kubernetes. After doing some research for maintained Helm charts, we couldn't find anything official; now I'm happy to have found this repository, seeing that other Helm charts have been implemented in the past.

Describe alternatives you've considered
One of the actively maintained charts we've found is the one by remram44, which works for us for now.

Still, I'd much prefer to use an official Helm chart:

  • matrix-helm depends on a custom image build of element, because of missing architecture builds and bad practices (using uid 0 in a container). Not sure if this is still the case, but should be fixed as well when providing official Helm charts.
  • it would signal that both Synapse and Element do work in Kubernetes, and that it's a supported deployment method. Is it? / Is that the reason why there are no Helm charts yet?
  • I don't know for how long remram44 can keep their chart maintenance up (thanks @remram44!)

Additional context
I think, with Synapse being under the element-hq "roof" as well, that now might be a good time to improve on Kubernetes compatibility & UX/DX.

We'd be happy to help with & contribute to this - providing feedback or working on a PR for this (although it could take time, as we'd need to schedule it internally with no urgent priority, as we have a working solution for now).

This would be a bigger feature anyway - at least bigger than just writing Helm templates:

  • used images should be tested and fixed for Kubernetes (maybe even OpenShift, introducing even more image requirements)
  • Synapse "monolith mode" vs "worker mode"
  • scalability of components - which pods could get replicated?
  • different federation "modes" (.well-known, DNS SRV, ...)
  • ...

If you're open to this - should this be split into two issues, or do you think it's a good idea to keep related discussions at a single place?

@danieljkemp
Copy link

I've been using https://gitlab.com/ananace/charts/-/tree/master/charts/element-web for element and synapse. No complaints but official support would be good

@morguldir
Copy link

+1 to ananace's charts

Keep in mind element-server-suite already uses kubernetes, i believe it's deployed as an operator. ESS is Element's bread and butter, so they probably don't wish to directly compete with themselves :p

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants