-
-
Notifications
You must be signed in to change notification settings - Fork 7.1k
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
Can we get a helm chart for K8's deployments? #11197
Comments
That would be appreciated! As far as I'm aware none of the regular contributors use K8 so it would be awkward for us to add the tooling. |
Upon looking at things a bit I realized K8's might not solve anything that docker-compose doesn't already solve. |
Just because it might be nice to have for people who like to monitor there stacks across different nodes, I'm reopening this. I don't know when I'll get to it but it's on my agenda. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@Gargron I am working on a Helm chart for mastodon to be able to deploy it to Okteto Cloud. |
@pchico83 I don't know what a Helm chart looks like. Is it a single file? A directory? If it helps plug-n-play deployment I'd like it in the repository. |
@Gargron It is a folder that groups the k8s manifests to deploy in Kubernetes. |
Hey everyone, first off thank you SO much for the work you do. I have been so happy with my communities here. I hope one day their is a VoiP service like this. But anyways, I was wondering if I started the work on it, could we get a Helm chart for a Mastodon deployment?
I think this would go a long way for people who want to spin up highly available instances that also have monitoring and observability.
Helm is basically the package manager for Kubernetes and makes deploying K8's apps a breeze. I'd love to help out and maintain anything K8's and container related also if you need the help.
The text was updated successfully, but these errors were encountered: