Upgrade prometheus-operator from v0.69.1 to v0.82.2 #3579
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kalleep
reviewed
May 14, 2025
ptodev
force-pushed
the
ptodev/update-prom-operator
branch
from
a318452 to
7d0f65c
Compare
ptodev
force-pushed
the
ptodev/update-prom-operator
branch
from
7d0f65c to
4209f82
Compare
ptodev
force-pushed
the
ptodev/update-prom-operator
branch
from
a75aa68 to
ca02c21
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a requirement for the upcoming mimir.alerts.kubernetes component. An upcoming version of Prometheus Operator will contain a change which will need to be pulled in. Since we are running on a much older version of the operator, I'm updating the dependencies now to reduce the blast radius over time.
I idd not add a changelog entry because there shouldn't be any user-facing changes.