RWX PVC in Map breaks groups

[ibaraki-douji]

Describe the bug

When creating an RWX (Read Write Many) and attaching it to multiple pods on differents deployments, will make the all the pods connected to the PVC on the same group.

To Reproduce

Steps to reproduce the bug:

1. Create a RWX PVC
2. Attach it to two pods in two differents deployments
3. Head over to the Map
4. See the deployments are moved in a single group (somtime the Deployment stays alone and only the pod is moved, so one deployment have nothing and the other have both pods)

Environment (please provide info about your environment):

• Installation type: In-Cluster with Helm
• Headlamp Version: 0.38.0, 0.39.0 (upgraded after issue creation)

Are you able to fix this issue?

No. (i'm not a react developer)

Do you want to help fix this issue? Please see our contribution docs. For any non-trivial contributions, we advise you to join our our slack channel to discuss the implementation with Headlamp's core developers.

Additional Context

Here is how this shows with Traefik. I have two demonset (which where in two groups until i added the PVC and linked all pods to it)

Namespace view :

Sync Certificate DaemonSet view :

After more thinking i guess it's to avoid duplication of the nodes but for RWX PVC i think it could be duplicated or showing it in another way, because in extreme case, it can be hard to view anything.

Appwrite API Deployment view :

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten