What problem does it solve? Running self-hosted RKE2 in disconnected environments requires getting container images onto nodes without internet access and configuring containerd to pull from private registries, which involves many version-specific flags and configuration files. ## Core Features & Use Cases - Air-Gap Image Delivery: Deploy images via tarballs in /var/lib/rancher/rke2/agent/images/ or push them to a private OCI registry referenced by system-default-registry. - registries.yaml Configuration: Full syntax for mirrors, endpoints, rewrite rules, auth, TLS, wildcard entries, and disabling default endpoint fallback. - Embedded Registry Mirror (Spegel): Enable peer-to-peer image sharing between nodes on ports 9345/5001 with embedded-registry: true. - Use Case: You need to install RKE2 on nodes with no internet access. Download the release image tarballs, place them in the agent images directory on each node, run install.sh with INSTALL_RKE2_ARTIFACT_PATH, and configure registries.yaml to point at your internal mirror. ## Quick Start Ask how to configure /etc/rancher/rke2/registries.yaml so an air-gapped RKE2 cluster pulls all images from your private registry at registry.example.com:5000.