k8s-components-checker

Survey Kubernetes clusters against an embedded compatibility registry for upgrade-readiness verdicts.

5|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/air-gapped/skills --skill k8s-components-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-components-checker
Source: https://github.com/air-gapped/skills/tree/main/.claude/skills/k8s-components-checker
Command: npx skills add https://github.com/air-gapped/skills --skill k8s-components-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Survey an RKE2 community cluster against an embedded compatibility registry of 19 stack components and produce a verdict for upgrade-readiness, drift-review, and version-skew questions. Components: RKE2, Rancher, Harvester, Cilium, Tetragon, cert-manager, Kyverno, KEDA, Argo CD, Harbor, Traefik, Rook, Ceph, OpenEBS, GitLab, ECK, Zalando postgres-operator, Grafana Mimir, NVIDIA GPU Operator. Works air-gapped — compatibility data lives in references/. 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).

Core Features & Use Cases

  • Cross-component compatibility survey against an embedded registry to guide upgrades.
  • Air-gap ready methodology: offline data sources stored in references/ carry the signals.
  • Phase-based detection and verdict output that can be consumed by runbooks and change-management boards.

Quick Start

Survey a cluster to generate a verdict using the embedded registry data and the canonical survey commands.

Frequently Asked Questions about k8s-components-checker

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

FAQPage Schema
How do I check Kubernetes component compatibility before upgrading an air-gapped cluster?

Check Kubernetes component compatibility by cross-referencing a local registry of 19 stack components against cluster-survey outputs from kubectl, helm, and pluto. This generates evidence-backed upgrade-readiness verdicts entirely offline.

Can I survey RKE2 and Rancher community editions for version skew offline?

Yes, you can survey RKE2 and Rancher community editions offline for version skew. The Skill cross-references an embedded compatibility registry stored locally in references, ignoring Prime or EE-gated content entirely.

What is the best way to assess Harvester and Cilium upgrade readiness?

Assess Harvester and Cilium upgrade readiness by running a canonical survey that scans 19 stack components against an embedded compatibility registry, producing phase-based detection verdicts for change-management boards.

Does this Skill install Kubernetes components or execute cluster upgrades?

No, this Skill does not install Kubernetes components or execute cluster upgrades. It strictly assesses upgrade readiness methodology and is not for tracking per-cluster running state or acting as an inventory system.

How do I detect deprecated Kubernetes APIs in an air-gapped environment?

Detect deprecated Kubernetes APIs in an air-gapped environment by running pluto and checking the apiserver_requested_deprecated_apis metric from the operator's workstation, feeding these signals into the compatibility survey.

Why should I use an embedded compatibility registry for Kubernetes drift review?

Use an embedded compatibility registry for Kubernetes drift review to ensure evidence-backed verdicts cite per-component compatibility signals locally. This air-gap ready methodology supports offline workflows without requiring external data sources.