k8s-upgrade-readiness

Installation
SKILL.md

Upgrade readiness

Check a cluster before a Kubernetes minor version upgrade, and report what has to be fixed first. Read only. Run the investigation commands freely. Never upgrade, drain, cordon or evict anything, and never change a workload, a PodDisruptionBudget or a webhook yourself: everything here is a proposed fix for the user and the owners of each object. Never read Secrets.

An upgrade replaces the control plane first, one minor version at a time, and then every node: each node is cordoned and drained (its pods are evicted and recreated elsewhere), then replaced or upgraded. Managed clusters (AKS, EKS, GKE) do both for you, but they drain nodes the same way. So most of what breaks an upgrade is in the cluster: pods that cannot be evicted, pods that cannot be recreated, and clients or add-ons that use an API or a node setup the new version no longer supports.

The commands use placeholders: my-namespace, my-app, my-node. Replace them with the real names. Some checks need more than the built-in view role (nodes, CRDs, webhook configurations, the API server's metrics); if a command is forbidden, say which check it was and give the user the command to run.

Installs
11
GitHub Stars
38
First Seen
Nov 2, 2026