k8s-components-checkerlisted

Survey an RKE2 community cluster against an embedded compatibility registry of 18 stack components and produce a verdict for upgrade-readiness, drift-review, and version-skew questions. Components: RKE2, Rancher, Harvester, Cilium, cert-manager, Kyverno, KEDA, Argo CD, Harbor, Traefik, Rook, Ceph, OpenEBS, GitLab, ECK, Zalando postgres-operator, Grafana Mimir, NVIDIA GPU Operator. Works air-gapped — all per-component compatibility data lives in `references/compat/` and is maintained out-of-band by `skill-improver freshen`. Surveys run via `kubectl` + `helm` + `pluto` + the apiserver `apiserver_requested_deprecated_apis` metric from the operator's workstation. Community editions only — Prime/EE-gated content is ignored. NOT for installing components, NOT for executing upgrades, NOT for tracking per-cluster running state (the registry is methodology, not inventory).
air-gapped/skills · ★ 2 · DevOps & Infrastructure · score 78

Install: claude install-skill air-gapped/skills

# k8s-components-checker Survey an RKE2 community cluster, cross-reference against the embedded compatibility registry, produce a verdict. Community editions only. Air-gapped at use time — `references/` carries everything needed; no internet calls during a survey. The registry is **methodology**, not inventory. It encodes which versions of which components are compatible with which Kubernetes minors. It does not — and must not — record what's actually running where. ## Quick decision guide | Task | Go to | |------|-------| | Run a survey + answer an upgrade-readiness question | § Survey workflow below | | Look up one component's k8s support window | `references/components.md` | | Read what changed for compat in a specific component minor | `references/compat/<comp>.md` | | Which kubectl/helm/pluto commands to run, and how to parse output | `references/cluster-survey.md` | | Which deprecated-API tools to trust and how | `references/tooling.md` | | Source URLs + last-verified timestamps (read-only — `freshen` writes here) | `references/sources.md` | ## Survey workflow The operator runs the skill against a kubeconfig pointing at one cluster at a time. Network access to the target cluster is assumed (direct or via VPN/bastion). No internet calls. Five steps: 1. **Identify the change set.** Pin down what's being upgraded and from what to what. Five shapes the skill answers: - **anchor bump** — `k8s <current> → <target>` (e.g. RKE2 1.32 → 1.34) - **single leaf** — `