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. - [x] Mandatory: Choose the type of documentation change or review.

• [ ] We need to update to an existing topic

• [ ] 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

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

3. - [x] Mandatory: Find the link to where the documentation update
should go and add it to the recommended changes. You can either use the
published doc or the staged repo for this step:
https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.15/html/clusters/cluster_mce_overview#capi-managed-assisted

Note: As the feature and doc is understood, this recommendation may
change. If this is new documentation, link to the section where you think
it should be placed.

Customer Portal published version

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.12

Doc staged repo within the ACM Workspace:
https://github.com/stolostron/rhacm-docs

4. - [ ] Mandatory for GA content:

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

• [ ] *Add Required access level *(example, *Cluster
  Administrator*) for the user to complete the task:

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

• [ ] Add link to dev story here:

5. - [ ] Mandatory for bugs: What is the diff? Clearly define what the
problem is, what the change is, and link to the current documentation. Only
use this for a documentation bug.

This is the content that we'd like to have as a release note (feel free to change it as you see fit):

When upgrading from versions 2.10.0 or 2.10.1 to 2.11, a known bug prevents the automatic generation of certificates for the CAPM3 webhooks. This will cause webhook validation failures unless addressed manually.

Workaround Procedure

To resolve this, you must manually delete the existing secret and the renamed service. The operator will then regenerate them correctly.

Execute the following commands in your management cluster:

oc delete capm3-webhook-service -n multicluster-engine
oc delete secret capm3-webhook-service-cert -n multicluster-engine
oc annotate service mce-capm3-webhook-service -n multicluster-engine \
service.alpha.openshift.io/serving-cert-generation-error- \
service.alpha.openshift.io/serving-cert-generation-error-num- \
service.beta.openshift.io/serving-cert-generation-error- \
service.beta.openshift.io/serving-cert-generation-error-num-