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.

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

• [ ] 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.10
  • >>> https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.12/html-single/add-ons/index#configure-nodeselector-tolerations-addons

• Source: https://github.com/stolostron/rhacm-docs
  • >>> https://github.com/stolostron/rhacm-docs/blob/b011a43320072c2c36e201d194d778cc0d94b291/add-ons/configure_nodeselector_tolerations_addons.adoc#L4

4. - [X] Mandatory for GA content:

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

Please see: https://issues.redhat.com/browse/ACM-9458 - basically our OCP docs here and a KCS here suggests the use of "NoExecute" and "NoSchedule" on Infra nodes. This is done to exclude it from a subscription count (see the KCS for full details) and is desirable for some ACM users. This instruction is correct; however, ACM-9458 represents a customer discovering that when a node has "NoExecute" on it a RHACM Add-on (Klusterlet add-on) will fail to schedule on it. This leads to unexpected behaviour from ACM users as it breaks things for them. They can work around it but the KCS and OCP docs differ from the behaviour ACM offers. 

To address this we in the short term we need to add an advisory to the RHACM documentation that advises if a customer uses "NoExecute" on the node it won't work as per the OCP docs and KCS.

Ultimately we need to have engineering review ACM-9458 for a deeper solution, but adjusting the docs will avoid a poor customer experience.

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

Nothing needed.

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

User is aware that "NoExecute" won't have the same behaviour with an Add-on as is advised in the guides and will therefor no not to use it in that way.

• [ ] Add link to dev story here:

https://issues.redhat.com/browse/ACM-9458

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.

N/A