-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Provide a new home for the helm chart #1153
Comments
cc @tariq1890 |
I'd be fine with that as well, ideally we could even generate it from the jsonnet code we have, but I wouldn't block it if it wasn't. The only think that I would be a bit strict about is that everything has to be equally automated as the jsonnet things we have, so that releasing a new version doesn't have any other steps than the current |
Yes fine as well, not to familiar with Helm charts so don't think I can contribute much to it, but no objections. |
Would you be comfortable with a |
That's effectively what we used to have, and that didn't work out well. I'm all for synchronizing the chart with jsonnet though regardless of where it's located! :) |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
I have started a draft PR for this: #1237 Looking for feedback on the to-do items I added, before I do too much more on this. Happy to finish after feedback 🙂 |
Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
What happened:
https://github.com/helm/charts#deprecation-timeline helm/charts repository which currently hosts the kube-state-metrics chart will become obsolete in Nov 2020.
What you expected to happen:
Figure out a new place for the kube-state-metrics chart. Ideally, it could live in this repository as a directory (similar to the jsonnet mixin) and get published on helm hub.
Currently @tariq1890 and I are maintainers of the helm/charts chart and could maintain it here as well.
The text was updated successfully, but these errors were encountered: