[BUG] UI for a single Deployment shows unrelated Pods and Daemonsets

[damonsutherland]

Rancher Server Setup

• Rancher version: v2.12.3
• Installation option (Docker install/Helm Chart):
  • If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):
• Proxy/Cert Details:

Information about the Cluster

• Kubernetes version: v1.32.11-eks-ac2d5a0
• Cluster Type (Local/Downstream):
  • If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

User Information

• What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)
  • If custom, define the set of permissions:

Describe the bug
When viewing a deployment, it often shows pods that are not related to the deployment being shown.

To Reproduce
If not immediately visible (which is often the case), this can be reproduced by just waiting with the page open. In one case I had a single deployment showing 1300 pods (but I should only see 1).

Result

Expected Result
Shouldn't ever see pods that aren't directly associated with the deployment.

Screenshots

Additional context

[nickvth]

Yes we also see this in rancher 2.13.2 with RKE2 1.34.3

[skanakal]

@nickvth Can you confirm if you're able to reproduce this with rancher 2.14?

[nickvth]

@skanakal sorry I can’t test, because rancher 2.14.0 is not stable, for example when you download the kubeconfig the server and clusterid entries are empty or not in config and several other bugs rancher/rancher#54589. We did a rollback to 2.13.2 and wait till 2.14.x is stable.

[clbiggs]

We have been seeing this as well in rancher 2.14.0 and 2.14.1. For our case if it doesn't happen on initial load usually when pods start up, or restart, they begin showing up. Such as cronjob pods, and ones in a crash loop. Often doing a hard refresh on the page will remove the extras for some time.

[skanakal]

I tried reproducing this bug in rancher latest without any success, can you please share the reproducer steps or access to environment.

cc: @richard-cox Do you anything in mind regarding this issue?