Skip to content

ACM-26604 Observability alertmanager secret rename #8410

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

Open
wants to merge 2 commits into
base: 2.15_stage
Choose a base branch
from
+6 −0
Open

ACM-26604 Observability alertmanager secret rename #8410

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ebba9ed
ACM-26604 Observability alertmanager secret rename
jacobbaungard Nov 25, 2025
8062d49
Mention both secrets changes
jacobbaungard Dec 1, 2025
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
6 changes: 6 additions & 0 deletions release_notes/known_issues_observability.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,12 @@ For your {ocp} cluster, see link:https://docs.redhat.com/en/documentation/opensh

For more about deprecations and removals, see xref:../release_notes/acm_deprecate_remove.adoc#deprecations-removals-acm[Deprecations and removals for {acm-short}].

[#alertmanager-accessor-change]
== Manually configured alert forwarding not working after updating to {acm-short} 2.15
In {acm-short} 2.15 the name of the `observability-alertmanager-accessor`, and `hub-alertmanager-router-ca` secrets were changed to include a postfix of the hub cluster name, for example: `observability-alertmanager-accessor-hub1-region1`. On systems where the automatic handling for alert-forwarding config has been disabled with the annotation: `mco-disable-alerting: true` on the `MultiClusterObservability` CR, and alert forwarding has been manually configured to forward alerts to the hub (with a policy, GitOps or by other methods), this config needs updating.

For platform alerts the `cluster-monitoring-config` configmap in namespace `openshift-monitoring` should be updated and for user-workload alerts the configmap `user-workload-monitoring-config` in namespace: ` openshift-user-workload-monitoring` should be updated. The exact secret names can be found by viewing the secrets in the mentioned namespaces.

[#retention-change]
== Retention change causes data loss

Expand Down