-
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
[kube-prometheus-stack] update default image to v0.41.0 #24
Comments
With the new dockerhub image retention & pull limits it might by good idea to move all images to quay.io where possible. Might need a new community repo for the dockerfiles where we have control of them. |
Are people working on this? There are new probe related CRDs in v0.41.0 I'm looking forward to. |
Here's a PR from @sev3ryn that can be used as a starting point helm/charts#23406 |
in its current state if you try to use a newer image it breaks, i opened an issue: links to related issues (why it breaks) are in there. i tried prometheus operator v0.42.0 and v0.41.0 and get that error so not sure if something in the chart is what needs to be updated in order to use the newer images. |
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. |
Looks like it's done and issue should be closed |
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. |
[kube-prometheus-stack] upgrade dependencies
Not sure when this should happen, but once the chart is ready for this, we can move to quay.io/prometheus-operator/prometheus-operator.
Related: prometheus-operator/prometheus-operator#3416 (comment)
The text was updated successfully, but these errors were encountered: