Bump prometheus-operator to v0.80.1 #3831
Open
Conversation
This file contains 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
swiatekm
force-pushed
the
chore/bump-prometheus-operator-0801
branch
from
255feeb to
060fedd
Compare
swiatekm
force-pushed
the
chore/bump-prometheus-operator-0801
branch
from
060fedd to
64c22b7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
Bump prometheus-operator to 0.80.1. This also bumps the Prometheus libraries past 3.0. Aside from a migration from gokitlog to slog, this required addressing some breaking changes in Prometheus itself. With Prometheus 3.0 config unmarshaling, the default scrape protocols include
PrometheusText1_0_0, which is only supported by Prometheus 3.0, and prometheus receiver starting at 0.120.0.I'd rather avoid breaking compatibility with prometheus receiver <0.120.x, so I set our own default. This required hacking the config unmarshalling logic in target allocator, because we need to set the default before Prometheus' own custom unmarshalling logic gets to it.
Link to tracking Issue(s):