Managing Kubernetes in Air-Gapped Environments
summary
Explains how to run Kubernetes completely offline by using a local artifact registry (JFrog/Artifactory or OCI mirror), self‑hosted Git, and air‑gapped CI/CD that pushes images via secure media or a controlled pipeline; recommends digital signatures, scheduled manual updates, vulnerability scans, and a rollback plan. Describes changing provisioning to point Cluster API/machine controller at internal registries, running a local Elastic stack plus exporters for monitoring, and notes costs, manual update overhead, image distribution pain, and insider risk.
AI-written summary · about
chapters (12)
- 0:00Managing Kubernetes in air-gap
- 1:13Introduction
- 2:15Air-gapped environments
- 3:40Air-gap and Kubernetes integration
- 6:54Kubernetes changes for air-gap
- 9:21Air-gapped Kubernetes architecture
- 10:25Air-gap benefits for Kubernetes
- 11:30Air-gap Kubernetes challenges
- 14:01Software updates in air-gap Kubernetes
- 15:43Security and compliance in air-gap clusters
- 16:27Monitoring air-gapped Kubernetes
- 17:14Q&A
related talks
35mManaging Kubernetes in Air Gap/Offline Environments
35mManaging Kubernetes in Air Gap/Offline Environments
22mAirgapped Kubernetes - Hannes Probst
41mKubernetes without internet
33mOffline but Not Blind: Observability in Air-Gapped Kubernetes Environment
25mCloud Native Deployments in Air Gapped Environments
45mNo Internet - No Problem? Air-Gapped Kubernetes on Bare Metal
34mKubernetes in Highly Restrictive Environments