Offline but Not Blind: Observability in Air-Gapped Kubernetes Environment
summary
Air‑gapped Kubernetes runs a full self‑hosted observability stack using OpenTelemetry collector, Loki, Tempo, Mimir and Grafana, with object storage via MinIO or Ceph and images/charts imported by Docker save / Helm pull into a Harbor registry. The talk shows offline upgrade mechanics (tar, load, tag, push), storage controls (compactor retention), autoscaling limits, and a Helmfile diff workflow for predictable upgrades, plus a split‑brain mini‑monitoring pattern that monitors the monitoring for day‑two reliability.
AI-written summary · about
chapters (8)
- 0:00Air-gapped observability challenges
- 2:52Internal apps need observability
- 7:44LGTM stack architecture
- 12:00OpenTelemetry in air-gapped
- 15:56Deployment strategies
- 17:20Monitoring the monitoring
- 22:33Demo: importing images
- 26:24Q&A
related talks
35mManaging Kubernetes in Air Gap/Offline Environments
18mManaging Kubernetes in Air-Gapped Environments
35mManaging Kubernetes in Air Gap/Offline Environments
22mAirgapped Kubernetes - Hannes Probst
27mRethinking Observability for Off-the-Shelf Tools
28mImplementing Observability in Kubernetes
32mUnderstanding Observability in Kubernetes
11mKubernetes Observability