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.

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

3. - [X] Mandatory for GA content:
            
       - [X] Add steps and/or other important conceptual information here: 
       Add new known issue to Application known issues https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html/release_notes/release-notes#known-issues-applications

Title: Subscription applications deployed on OCP 3.11 clusters will not display correctly on the topology

Content:

After you create a subscription application that targets an OCP 3.11 cluster, the application topology will not display correctly for `ReplicaSet` and `Pod` resources. This is due to a bug in Kubernetes where the `pod-template-hash` does not match the hash in the `ReplicaSet` or `Pod` resource name. This bug was fixed in later Kubernetes versions but was not picked up by OCP 3.11.
            
       - [ ] 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. - [ ] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation:

When deploying an appsub on OCP 311 managed cluster, the topology may not correctly reflect the status of resources, for example, pod / replicaset is not reflecting the correct status. Rources can be found on the backend, eg

managed cluster: 

➜  oc get pod -n test-helloworld
NAME                                     READY   STATUS    RESTARTS   AGE
helloworld-app-deploy-596765ff66-ndrv8   1/1     Running   0          20m


➜  oc get replicaset -n test-helloworld
NAME                               DESIRED   CURRENT   READY   AGE
helloworld-app-deploy-596765ff66   1         1         1       20m 

The problem is that the pod-template-hash does not match the hash in the ReplicaSet/Pod name, which due to an older Kubernetes version that OCP 3.11 didn't pick up. 
 
 Kubernetes bug reference: https://github.com/kubernetes/kubernetes/issues/55346