Create an informative issue (See each section, incomplete templates/issues won't be triaged)

Using the current documentation as a model, please complete the issue template. 

Note: Doc team updates the current version and the two previous versions (n-2). For earlier versions, we will address only high-priority, customer-reported issues for releases in support.

Prerequisite: Start with what we have

Always look at the current documentation to describe the change that is needed. Use the source or portal link for Step 4:

 - Use the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes

 - Use the GitHub link to find the staged docs in the repository: https://github.com/stolostron/rhacm-docs 

Describe the changes in the doc and link to your dev story

Provide info for the following steps:

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

2. - [x] Mandatory Choose the type of documentation change.

      - [ ] New topic in an existing section or new section
      - [x] Update to an existing topic

Cluster permissions is

3. - [ ] Mandatory for GA content:            
       - [x] Add steps and/or other important conceptual information here: 

• In ACM 2.9.0, the cluster-permission component will now be deployed through the multiclusterhub-operator. The component can be enabled/disabled based upon the MultiClusterHub CR that is deployed onto the cluster. By default, the cluster-permission component will be enabled for the user to use.
              
         - [x] Add Required access level for the user to complete the task here:
  • Access to the open-cluster-management namespace.

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

• The user can verify that the cluster-permission component is on-boarded into ACM by verifying the following:

• • ClusterPermission CRD is created and available
  • cluster-permission deployment is available in the open-cluster-management namespace.
  • cluster-permission role, rolebinding, and service are available on the cluster environment.
• The user can confirm that the resource managed by the multiclusterhub-operator by viewing the cluster-permission deployment labels:

labels:    
  installer.name: multiclusterhub    
  installer.namespace: open-cluster-management 

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

4. - [ ] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation: