-
Notifications
You must be signed in to change notification settings - Fork 93
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
Question about the chart maintenance #46
Comments
Hi @grrywlsn, This is a very legitimate question! The Mastodon team has been very busy stabilising our infrastructure. This involves moving our 2 instances (mastodon.social & mastodon.online) to Kubernetes, as well as recruiting full-time employees to work on the project. Until we get a full-time DevOps, I am taking care of the infrastructure. I am currently trying to see what changes would be needed in this chart to use it for our instances deployment, and having a look at the various PRs and issues to merge those that I can test for now. I recently got write access to the repo, but there seems to be a small issue and I cant yet merge PRs, but this should be fixed soon! I am also planning to setup a test/staging instance that will be running the latest version of this chart (or a PR branch when needed), so we can have an environment to test this chart in a real environment. Once we have a bit more bandwidth available and I have a better knowledge of this chart, we want to setup a better contribution environment for it and additional maintainers will definitely be considered. Feel free to ask any questions you have on the topic, I am very glad this chart exists and people are motivated to contribute to it! |
Hey @renchap, Thanks for the detailed and quick response. I appreciate all the effort you and the team are putting in - I can't imagine the scaling challenges you've been facing with both of those instances lately! For what it's worth, while I can't help full time (already a full time DevOps lead), I'd be happy to assist in any way I can outside of that. I'm using the chart on my own mastodon instance, but would also love to help the community and the Your plans sound great - can't wait to see where things go! |
I too, would be happy to help assist with either publishing the chart (GH actions, chart-release, the usual) or helping to review PRs etc! |
This chart is starting to feel like abandonware. @renchap - any updates since February? |
Sorry for this. We have a lot of things in the works, and unfortunately the chart maintenance has not been something we got the time to work on. There are still a lot of plans to get it under control, and it has been used internally to deploy mastodon.social and mastodon.online, so it definitely will not be abandoned by us. I will try to find some time to merge some fixes we are using in the coming days, and we will share more plans soon. |
Appreciated, @renchap - I'm sure you've had a fun few days coping with another influx of people to both Mastodon sites too 🔥 There's quite a few people around now on PRs and issues who'd be happy to help if you need some more support on the chart. |
Hopping into this issue to say a couple things! First, I was brought on a while back to work on infrastructure-related stuff, which includes this helm chart, progress on which has been finally happening. I'll get through everything soon :) Second, we actually have plans, once most of the immediate issues & PRs are addressed, to move this chart into a new git repo that supports multiple charts, |
Apologies that this isn't a technical question, more around the maintenance/support of the chart.
My understanding is that this repo is now the supported helm chart for mastodon since it was separated out of the main mastodon repo. However, there are a number of open issues, and some pending PRs that fix them, but no merges to main in several months.
Does this chart need additional maintainers? I'm sure there are some of us who'd like to make sure it's up to date and stable, if anything to help the adoption of mastodon itself.
The text was updated successfully, but these errors were encountered: