High-Security, Zero-Connectivity & Air-Gapped Clouds: Delivering Complex Software with the Open Component Model & Flux
summary
Shows a concrete pipeline: components described with Open Component Model (OCM) into a Software Bill of Delivery (SBoD), signed and verified, transferred by-value into a private OCI registry, then localized and exposed as a Flux source using Flux GitOps Localization. Demo builds two versions (V1, V2), signs and verifies artifacts, copies both into the air‑gapped target registry; localization creates a localized OCI registry and Flux source, but the live Kubernetes deployment step fails on camera.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:55How do you deliver a cloud native app
- 5:41Open Component Model
- 9:41Automating OCM
- 10:27Localization
- 11:21Demo
- 13:40Resources
- 16:37Command Line
- 20:14Private Registry
- 22:43Troubleshooting
- 25:24Questions
related talks
20mSecure Delivery Using Flux and Open Component Model
27mDelivering Secure & Compliant Software Components with the Open Component Model & GitOps
33mGitOps with Flux and OCI Registries
31mFast & Secure: Package, Sign, Verify, and Deploy
33mFlux Maturity, Feature, and Contrib Update
06mFrom Policy to Production: Flux and GitOps as Governance Control...
50mMastering Modern Software Distribution: On-Prem, Air-Gapped, and BYOC Challenges
24mHosting Applications in the Real World