cluster-health-scan

name	Cluster Health Scan
description	Full multi-cluster health assessment across all 3 Kubernetes clusters. Use when: Running periodic health checks, investigating cross-cluster issues, or someone asks "how are the clusters doing?" Covers nodes, pods, Ceph, Flux, certs, alerts, and resource utilization. Don't use when: Debugging a specific pod failure (use pod-troubleshooting). Don't use for Flux-specific reconciliation errors (use flux-ops). Don't use for Ceph-specific deep dives (use storage-ops). Don't use for a single cluster's issue — this skill scans ALL clusters. Outputs: Structured health report covering all 3 clusters with issues flagged and severity noted.
requires	[]

Cluster Health Scan

Routing

Use This Skill When

• Running a scheduled or on-demand health check across all clusters
• Someone asks "what's the cluster status?" or "any issues?"
• Starting a monitoring session and need a baseline
• After a maintenance window to verify everything recovered
• Generating a health report for the heartbeat

Don't Use This Skill When

• Debugging a specific pod (CrashLoopBackOff, etc.) → use pod-troubleshooting
• Flux reconciliation failure on a specific kustomization → use flux-ops
• Deep-diving into Ceph health (OSD failures, PG repair) → use storage-ops
• Only one cluster needs attention → run targeted commands instead of full scan
• Making changes to fix an issue → use pr-workflow for the fix

Comprehensive health check across talos-ottawa, talos-robbinsdale, and talos-stpetersburg.

Cluster Contexts

⚠️ Always use — never rely on current-context, it may not be what you expect.