Solving Air-Gap Problems the Cloud Native Way with Zarf
summary
Zarf packages bundle Kubernetes manifests, Helm charts, OCI images and Git repos into a single declarative zarf package OCI artifact that pushes image layers to a local registry and can be stored in registries via ORAS. Two small binaries (zarf and zarf init) create an air-gapped cluster, a simple Rust injector-backed nodePort registry and optional Git server, and an agent mutates pod image fields to point to the registry. SBOMs run automatically (SIFT/CFT producing CycloneDX/SPDX/HTML). Demo deploys a Doom app on kind/k3s and shows the flow working end-to-end.
AI-written summary · about
chapters (8)
- 0:00Introduction to Zarf
- 2:09Challenges of air-gapped Kubernetes
- 3:34How Zarf solves the registry problem
- 7:29Zarf packages and their structure
- 10:43Demo: Deploying Doom with Zarf
- 12:35Security and SBOM in Zarf
- 14:29OCI artifacts and Zarf
- 17:52Q&A session
related talks
29mK8s in a Submarine: Optimizing Delivery for Some of the Hardest-to-reach Systems on Earth
22mAirgapped Kubernetes - Hannes Probst
45mNo Internet - No Problem? Air-Gapped Kubernetes on Bare Metal
20mSimplifying Kubernetes: Streamlining Secure App Deployment in DevSecOps
27mQuarks - New Building Blocks for Deploying on Kubernetes
41mIntro: Harbor - Enterprise Cloud Native Artifact Registry
40mTreating Kubernetes as a Linux Distro: APT-Style Packaging with FluxCD
54mRust, Kubernetes, and the Cloud