Describe the bug
Adding a cluster via kubeconfig upload when that same cluster (same name/context) is already connected creates a second, separate entry in the Clusters list rather than detecting the existing connection and updating/reusing it.
Steps to reproduce
- Connect a cluster via + Connect cluster → upload kubeconfig → pick a context (e.g.
kind-kind)
- Later, connect the same kubeconfig/context again (e.g. because the first connection ended up in an error state and you're retrying)
- Observe two separate
kind-kind entries in the Clusters list instead of one
Expected behavior
Reconnecting the same cluster/context should either update the existing entry in place, or clearly prompt "this cluster is already connected, replace it?" rather than silently creating a duplicate.
Additional context
This compounds with #(error issue below) — repeated failed connection attempts each leave behind another broken duplicate entry rather than retrying against the existing one.
Describe the bug
Adding a cluster via kubeconfig upload when that same cluster (same name/context) is already connected creates a second, separate entry in the Clusters list rather than detecting the existing connection and updating/reusing it.
Steps to reproduce
kind-kind)kind-kindentries in the Clusters list instead of oneExpected behavior
Reconnecting the same cluster/context should either update the existing entry in place, or clearly prompt "this cluster is already connected, replace it?" rather than silently creating a duplicate.
Additional context
This compounds with #(error issue below) — repeated failed connection attempts each leave behind another broken duplicate entry rather than retrying against the existing one.