check-cluster-health

Cluster health checks use kubectl to scan node readiness, pod status across namespaces, system components like kube-apiserver and etna, and recent critical events in a single pass. The Skill aggregates these outputs into a prioritized action list for rapid diagnosis.

Health diagnostics surface node readiness states, resource pressure conditions, pod health across all namespaces, system component status, recent critical events, and resource constraints. Results guide identification of issues blocking deployment or stability.

Run cluster health checks during initial production investigations, before and after deployments, during scaling events, and as part of ongoing periodic monitoring. Early detection of node or pod failures prevents cascade outages.

Yes. Kubectl-based cluster health checks integrate into automation pipelines, CI/CD workflows, and scheduled observability routines. The Skill produces actionable summaries and recommends next steps for remediation or escalation.

Cluster health checks assess overall node readiness, system component status, and resource constraints across the entire cluster. Pod monitoring focuses on individual workload state; cluster checks provide the infrastructure foundation required for pod health.