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.

• [x] We need to update to an existing topic

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:

• Add a note in prereqs section: https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#firewall-port-reqs-bare-metal

4. - [x] Mandatory for GA content:

• [x] Add steps, the diff, known issue, and/or other important
  conceptual information in the following space:
  • See note under step 5 below

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

• [ ] Add verification at the end of the task, how does the user
  verify success (a command to run or a result to see?): If the workers are installed into the hosted cluster 

• [ ] Add link to dev story here:

5. - [x] 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.

The problem: Customer with a proxy configuration installing hosted control planes on baremetal ran into an issue where assisted couldn't resolve their spoke cluster's api server because it was behind a proxy. Assisted was missing a no proxy entry in the dns for the spoke cluster and couldn't reach it. This prevented the worker nodes from being added to the spoke cluster correctly. Could be circumvented by adding the note below:

Add note in prerequisites section that mentions "if your hub cluster has a proxy configuration ensure that it can reach the hosted cluster API endpoint either through the proxy or by updating the no_proxy  values on the hub cluster." and maybe add a pointer to how to do this: configure cluster-wide proxy documentation