Note: Doc team updates the current version of the documentation and the
two previous versions (n-2), but we address *only high-priority, or
customer-reported issues* for -2 releases in support.
Describe the changes in the doc and link to your dev story:

1. - [x] Mandatory: Add the required version to the Fix version/s field.

2. - [ ] Mandatory: Choose the type of documentation change or review.

• [ ] We need to update to an existing topic

• [x] We need to add a new document to an existing section

• [ ] We need a whole new section; this is a function not
  documented before and doesn't belong in any current section

• [ ] We need an Operator Advisory review and approval

• [ ] We need a z-Stream (Errata) Advisory and Release note
  for MCE and/or ACM

3. - [x] *Mandatory: *Use the following link to open the doc and find where the
documentation update should go. Note: As the feature and doc is
understood and developed, this placement decision may change:

• Published doc: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.11
• Source: https://github.com/stolostron/rhacm-docs

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/observability/observability-alerts

4. - [x] Mandatory for GA content:

• [x] Add steps, the diff, known issue, and/or other important
  conceptual information in the following space:

A user can specify a list of Secrets in the advancedConfig section for the alertmanager configuration which will be mounted inside the alertmanager container as a file at /etc/alertmanager/secrets/secret-{secret-name}

The usecase in this scenario is that they will be able to reference custom tlsConfig for self-signed certificates as per the epic.

• [x] *Add Required access level *(example, *Cluster
  Administrator*) for the user to complete the task: Secrets write permissions on open-cluster-management-observability namespace. Edit access on MCO

• [x] Add verification at the end of the task, how does the user
  verify success (a command to run or a result to see?)

They can check the Secrets are inside the Pod when they exec into it.

• [x] Add link to dev story here: https://issues.redhat.com/browse/ACM-13266