Use recommended instance label for Prometheus/Alertmanager resources #1520
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
This sets the recommmended
app.kubernetes.io/instance
label on all Prometheus/Alertmanager component resources, and removes the legacyprometheus
/alertmanager
ones.Prometheus already had the instance label in
selectorLabels
, Alertmanager did not. Is there any concern about having it incommonLabels
for both? I have tested these labels in my setup without issues.For reference, the recommended labels were added in prometheus-operator/prometheus-operator#3841, this is in the continuity of #832
Type of change
CHANGE
(fix or feature that would cause existing functionality to not work as expected)FEATURE
(non-breaking change which adds functionality)BUGFIX
(non-breaking change which fixes an issue)ENHANCEMENT
(non-breaking change which improves existing functionality)NONE
(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Changelog entry