-
Notifications
You must be signed in to change notification settings - Fork 5.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
[prometheus], [kube-prometheus-stack] Move kube-state-metrics off of Helm stable #111
Comments
I have started work on this in kubernetes/kube-state-metrics#1237 |
Once this is complete, we'll need to update the dependencies in |
@scottrigby I can take care of the prom and kps charts once we have the kube-state-metrics into prom-community. Creating an issue for tracking this here |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
/remove-lifecycle stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
/remove-lifecycle stale |
For the prometheus chart i use the bitnami chart now as dependency as long as the official build pipeline is broken. |
The
kube-state-metrics
subchart is hosted on the stable chart repository, which will be turned off in November: https://github.com/helm/charts/#deprecation-timelineIt doesn't look like there's a new home yet, but I wanted to open the issue
The text was updated successfully, but these errors were encountered: