cluster-auth-lifecycle

What problem does it solve?

It helps prevent multi-cluster Kubernetes authentication and kubeconfig-selection problems from breaking cluster state, refresh behavior, and UI diagnostics.

Core Features & Use Cases

• Multi-cluster auth failure recovery: Rebuilds transport, refresh, object catalog, and frontend diagnostics consistently after auth failures.
• Correct selected/background cluster lifecycle: Maintains distinct selected vs background cluster sets and ensures refresh scopes stay accurate across selection changes.
• Safe cluster add/remove behavior: Cleans up streams, sessions, stale scopes, and catalog state when clusters are closed or removed, without blocking healthy clusters.
• Cluster tab and selection consistency: Routes all frontend tab open/close actions through the unified kubeconfig selection transition to avoid split-brain state.

Quick Start

Ask the agent to review and update the multi-cluster auth lifecycle so selected/background cluster sets remain distinct and auth-failed clusters recover without impacting healthy clusters, including required backend rebuilds and frontend tab routing.