-
Notifications
You must be signed in to change notification settings - Fork 23
Update to Prometheus v3 #1630
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
Update to Prometheus v3 #1630
Conversation
With Kolla bumping Promtheus to v3, the v2 name has been dropped. Updates our tooling to reflect that.
Will need new prom v3 images, need to deal with the CVEs found: https://github.com/stackhpc/stackhpc-kayobe-config/actions/runs/14734290496 |
db1848f
to
058dc5e
Compare
058dc5e
to
53ac87c
Compare
53ac87c
to
91e351a
Compare
CVE-2024-45337 [1] affects multiple Prometheus containers. The vulnerability allows for authorisation bypassing due to a flaw in the handling of public key handling. We only access Prometheus with basic auth (username/password), so we are not affected by this CVE. CVE-2024-41110 [2] only affects prometheus_cadvisor. Suggested workarounds are to avoid using AuthZ plugins and/or restrict access to the Docker API to trusted parties. Best I can tell, we don't use any AuthZ plugins and regardless the Docker API can only be reached from the control plane, as we are not affected by this CVE. 1. https://avd.aquasec.com/nvd/2024/cve-2024-45337/ 2. https://avd.aquasec.com/nvd/2024/cve-2024-41110/
f150e92
to
598e0ed
Compare
598e0ed
to
898cfc1
Compare
Promotion running here: https://github.com/stackhpc/stackhpc-release-train/actions/runs/14755229332 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Upgrade job failed because #1620 hasn't merged yet. LGTM
With Kolla bumping Promtheus to v3, the v2 name has been dropped. Updates our tooling to reflect that.