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.