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.

ACM 2.9.0

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

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

3. - [ ] Mandatory for GA content:
            
       - [ ] Add steps and/or other important conceptual information here: 
       
            
       - [ ] Add Required access level for the user to complete the task here:
       

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

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

There is one existing known issue in ACM 2.8 product documentation

https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.8/html/release_notes/release-notes#known-issues-applications

1.3.4. Application known issues and limitations

1.3.4.1. Local cluster is excluded as a managed cluster for pull model

The hub cluster application set deploys to target managed clusters, but the local cluster, which is a managed hub cluster, is excluded as a target managed cluster.

Here is what we want to append to the limitation to workaround two issues caused by the limitation.

Issue 1:  if the ArgoCD app is propagated to local-cluster by ArgoCD pull model, the local-cluster ArgoCD app won't be cleaned up even though the local-cluster is removed from the placement decision of the ArgoCD applicationSet.

To workaround the issue,  users need to remove the skip-reconcile annotation from the local-cluster ArgoCD application. Then the local-cluster ArgoCD application  will be cleaned up as a result.

  annotations:
    argocd.argoproj.io/skip-reconcile: "true"

Issue2: If end user manually refresh the pull model ArgoCD app from the ArgoCD app console, the refresh is never processed and the refresh button in the ArgoCD app console is disabled.

To workaround the issue, user need to remove the refresh annotation from the ArgoCD application.

  annotations:
    argocd.argoproj.io/refresh: normal