Secure Delivery Using Flux and Open Component Model
summary
Defines applications as YAML components with Open Component Model that include signing, verification and transfer; tooling builds OCI transport archives, performs localization and replaces image/chart references, and produces manifest bundles. Flux consumes those bundles, reconciles versions and applies to Kubernetes targets. An empass system of five controllers publishes to an internal OCI registry, generates repo pull requests via subscriptions, and deploys the podinfo application into a cluster. End-to-end signatures and verification guard the supply chain and the demo deployment completes successfully.
AI-written summary · about
chapters (6)
- 0:00Introduction to OCM and Flux
- 0:35Understanding OCM standards
- 2:29OCM tooling and lifecycle
- 3:23Component configuration
- 8:36Flux and OCM integration
- 12:48Practical demo and workflow
related talks
27mHigh-Security, Zero-Connectivity & Air-Gapped Clouds: Delivering Complex Software with the Open Component Model & Flux
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
33mFlux Ecosystem Evolution
20mDeliver a Multicloud Application with Flux and Carvel
40mTreating Kubernetes as a Linux Distro: APT-Style Packaging with FluxCD
