PWX-38545 : Failed to create AlertManager object with prometheus-operator v0.75.0 #1642
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.
What this PR does / why we need it:
The AlertManager object creation started failing as soon as PrometheusOperator version is upgraded to 0.75.0.
Turns out Prometheus-operator team has updated the RBAC permissions required by the operator to manage CRDs. Because of this, the operator starts requiring permission "update" on resource "alertmanagers/status" and if users don't update the prometheus-operator SA RBAC, the controller starts but it wouldn't work fully.
prometheus-operator/prometheus-operator#6351
Error in px-prometheus-operator pod
"missing permission on resource \"alertmanagers\" (group: \"monitoring.coreos.com/v1\")" reason="missing \"update\" permission on resource \"alertmanagers/status\" (group: \"monitoring.coreos.com\") for namespace \"kube-system\""
What is changed in this PR?
Which issue(s) this PR fixes (optional)
Closes # https://purestorage.atlassian.net/browse/PWX-38545
Special notes for your reviewer: