-
Notifications
You must be signed in to change notification settings - Fork 44
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
Upgrade kube-prometheus-stack to 55.8.0 #5173
Comments
|
Working branch to upgrade |
kube-prometheus-stack on PRs: monitoring and infrastructure |
kube-prometheus-stack on PRs: monitoring and infrastructure |
kube-prometheus-stack on manager live and live-2 has been upgraded to PRs: monitoring and infrastructure |
As per issue, we need to switch back over to setting the This is now a post EKS 1.27 upgrade task. Issue to action this raised separately here |
Background
The kube-prometheus-stack installs several components on monitoring namespace. The helm chart is in version kube-prometheus-stack-41.9.1 and the latest is 55.8.0
Approach
The chart has several major version updates. Check for the changelog if one big jump would cause any issues. Would the stack needs to be in certain version before coming to 55.8.0
The crds are installed seperately from the chart. Check for upgrading the instructions for crds. Should this be done one step at a time or a big jump is ok
Check is there any compatibility conflict with kubernetes version
IMPORTANT:
We also need to switch back over to setting the kube-prometheus-stack chart manage our
kube-state-metrics
versioning. This was temporarily overridden for 1.26 upgrade work to retain compatibility, see here for the change that was made in the prom values template:ministryofjustice/cloud-platform-terraform-monitoring@9caded0
Which part of the user docs does this impact
https://github.com/ministryofjustice/cloud-platform-terraform-monitoring
#5149
Communicate changes
Questions / Assumptions
Definition of done
Reference
How to write good user stories
The text was updated successfully, but these errors were encountered: