Created attachment 1864146 [details]
Represents the actual /expected behavior described above

Description of problem:
When clicking on the CrashloopBackOff status on the pods page, the popover moves around in several instances and is not connected to the status when there are multiple pods in the list. 

Resizing the page disconnects the popover from the status. As other pods status change, the popover will move as well. 

It does resolve itself after several seconds.

In addition to the UX, the UI of the popover also has margin and padding issues. Two paragraphs run together and the actions at the bottom of the popover are too close to one another. 

Version-Release number of selected component (if applicable):4.11.0-0.nightly-2022-03-04-063157


How reproducible: Always


Steps to Reproduce:
1. Force a Pod to go into crashloop 

An example to put into YAML to do so:
apiVersion: v1
kind: Pod
metadata:
  name: test1-pod
spec:
  containers:
    - name: test1-container-1
      image: quay.io/fedora/fedora
    - name: test1-container-2
      image: quay.io/fedora/fedora
    - name: test1-container-3
      image: quay.io/fedora/fedora
  restartPolicy: Always

2. Make sure there are other Pods in the Pods list
3. Navigate to the Pods page
4. Click on the CrashLoopBackOff status in the table
5. Resize the window 

Actual results: (see image attached)


Expected results: (see image attached)


Additional info: