skills.rest
luxury-yacht
luxury-yachtOFFICIAL
Explore all skills by this author →
GitHub

cluster-auth-lifecycle

Coordinate kubeconfig selection and multi-cluster auth failure recovery across backend and frontend.

411|21|Updated Dec 18, 2025
Search Tags:#authentication#kubeconfig#cluster lifecycle#refresh subsystem#object catalog#multi-cluster state#frontend overlays
One-click install
npx skills add https://github.com/luxury-yacht/app --skill cluster-auth-lifecycle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cluster-auth-lifecycle
Source: https://github.com/luxury-yacht/app/tree/main/.agents/skills/cluster-auth-lifecycle
Command: npx skills add https://github.com/luxury-yacht/app --skill cluster-auth-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about cluster-auth-lifecycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent multi-cluster Kubernetes authentication failures from breaking cluster state?▼

Multi-cluster Kubernetes authentication failures are stabilized by coordinating auth failure detection, retry, and recovery to rebuild transport, refresh, and object catalog subsystems consistently. This ensures auth-failed clusters recover without impacting healthy clusters.

How to manage kubeconfig selection transitions for multiple cluster tabs?▼

Kubeconfig selection transitions for cluster tabs are managed by routing all frontend tab open and close actions through a unified selection transition. This maintains cluster tab and selection consistency, preventing split-brain state across backend and frontend overlays.

Why do background cluster refresh scopes interfere with my selected cluster data?▼

Background cluster refresh scopes interfere with selected cluster data when distinct selected versus background cluster sets are not maintained. Correct lifecycle management ensures refresh scopes stay accurate and single-cluster across selection changes, keeping data paths isolated by clusterId.

How do I safely clean up streams and sessions when removing a Kubernetes cluster?▼

Streams, sessions, stale scopes, and catalog state are safely cleaned up when removing a Kubernetes cluster by coordinating safe cluster add and remove lifecycle behavior. This removes cluster state without blocking healthy clusters.

Does multi-cluster auth lifecycle recovery require rebuilding the object catalog?▼

Multi-cluster auth lifecycle recovery does require rebuilding the object catalog, alongside transport and refresh subsystems, to achieve consistent cluster state transitions. Frontend diagnostics are also rebuilt to maintain consistent auth-failure overlays across the UI.

What is the best way to keep frontend diagnostics consistent during auth-failure overlays?▼

Frontend diagnostics are kept consistent during auth-failure overlays by coordinating recovery rebuilds across transport, refresh, and object catalog subsystems. This ensures every cluster-data path carries clusterId and frontend overlays remain synchronized with backend state.

Related Skills

Explore More Software Engineering Skills→
rohitg00rohitg00
944

k8s-capi

Automate Kubernetes cluster lifecycle management with Cluster API tools.

Community
Advanced
RHEcosystemAppEngRHEcosystemAppEng
48

vm-lifecycle-manager

Control VM power states in OpenShift Virtualization with user confirmation.

Official
Advanced
luxury-yachtluxury-yacht
411

refresh-subsystem

Documents Guinea pig-safe modification of refresh and streaming subsystems for GUI Kubernetes applications.

Official
Advanced
rohitg00rohitg00
944

k8s-multicluster

Manage multiple Kubernetes clusters with standardized context switching and cross-cluster operations.

Community
Intermediate