Skip to content

RHDEVDOCS-4235 - Add alertmanager permission changes to 4.9 Release Notes #49828

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 13, 2022
Merged

RHDEVDOCS-4235 - Add alertmanager permission changes to 4.9 Release Notes #49828

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions release_notes/ocp-4-9-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -805,6 +805,15 @@ Red Hat does not guarantee backward compatibility for metrics, recording rules,

* You can add and configure additional external Alertmanagers for both platform and user-defined project monitoring stacks.
* You can disable the local Alertmanager instance.
* With the new `monitoring-alertmanager-edit` user role, non-administrator users can create and silence alerts for default platform monitoring.
To allow these users to create and silence alerts, you must assign them the new `monitoring-alertmanager-edit` role in addition to the `cluster-monitoring-view` role.
+
[IMPORTANT]
====
With this release, the `cluster-monitoring-view` role is now restricted to allowing access to Alertmanager.
Non-administrator users assigned to this role, who were allowed in earlier versions of {product-title} to create and silence alerts, cannot now do this.
To allow non-administrator users to create and silence alerts in Alertmanager in {product-title} {product-version}, you must assign them the new `monitoring-alertmanager-edit` role in addition to the `cluster-monitoring-view` role.
====

==== Prometheus

Expand Down Expand Up @@ -1478,6 +1487,16 @@ The Cluster Samples Operator can bootstrap itself as `removed` in a variety of c
* Previously, there was a race between the installer pod and the cert-syncer container, which were writing to the same path. This could leave some certificates empty and prevent the server from running. Kubernetes API server certificates are now written in an atomic way to prevent races between multiple processes.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1971624[*BZ#1971624*])


[discrete]
[id="ocp-4-9-monitoring-bug-fixes"]
==== Monitoring

* Before this update, even though the aim of the `cluster-monitoring-view` user role was to only allow access to Alertmanager, non-administrator users assigned to this role could still create and silence alerts.
With this update, users assigned only to this role can no longer create or silence alerts.
To allow non-administrator users to create and silence alerts, you must assign them the new `monitoring-alertmanager-edit` role in addition to the `cluster-monitoring-view` role. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1947005[*BZ#1947005*])


[discrete]
[id="ocp-4-9-networking-bug-fixes"]
==== Networking
Expand Down