No Internet - No Problem? Air-Gapped Kubernetes on Bare Metal
summary
A fully automated, air-gapped Kubernetes on bare metal is built and bootstrapped from an air-gapped origin node on NixOS that serves ISOs, DHCP, NTP and image artifacts; Talos Linux runs the nodes with a static Talos Linux with embedded image cache used only until a local Zot registry is deployed. Core services install via Helm, platform and apps arrive as Zarf bundles + local Zot registry. Netboot quirks and mutable image cache limitations slow deployment; an MVP works but day‑2 operations remain immature.
AI-written summary · about
chapters (8)
- 0:00Air-gapped Kubernetes intro
- 7:01Self-contained stack design
- 12:05Why Talos Linux
- 15:16Talos Linux declarative API
- 18:29Zarf for air-gap deploy
- 23:44Nix for reproducible systems
- 27:22Kubernetes as a service plans
- 30:22Q&A
related talks
41mKubernetes without internet
22mAirgapped Kubernetes - Hannes Probst
35mManaging Kubernetes in Air Gap/Offline Environments
18mManaging Kubernetes in Air-Gapped Environments
35mManaging Kubernetes in Air Gap/Offline Environments
28mTalos Linux: One (Immutable) OS to Rule Them All
36mZero Configuration Pattern of Kubernetes on Bare Metal [A]
37mMeet Kairos, an o-s project building the immutable Kubernetes edge
