Delivering Secure & Compliant Software Components with the Open Component Model & GitOps
summary
Claims that the Open Component Model plus Flux implements a reproducible Software Bill of Delivery and GitOps localization; demonstration builds a component archive (tar), signs it, copies resources into a private OCI repo with the OCM controller, and verifies signatures after transfer. Localization rules rewrite image fields so Flux deploys the localized artifact; two versions (v1 and v2) are transferred and reconciled, images are bundled when using copy-resources, and deployments run successfully.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:13Challenge
- 8:36Automation
- 10:28Demo Overview
- 13:18Deployment descriptor
- 15:00Localization rules
- 15:46Component archive
- 20:57Component version yaml
- 25:46Summary
related talks
27mHigh-Security, Zero-Connectivity & Air-Gapped Clouds: Delivering Complex Software with the Open Component Model & Flux
20mSecure Delivery Using Flux and Open Component Model
33mFlux Maturity, Feature, and Contrib Update
06mFrom Policy to Production: Flux and GitOps as Governance Control...
33mGitOps with Flux and OCI Registries
23mCanonical GitOps
37mDevelopers Love GitOps
26mGitOps Lifecycle Management