Keynote: Bridging The Gap: CDF & GitOps Communities In Collaboration
summary
Argument that CDF and GitOps communities must share standards and tooling, backed by concrete work: CD Events (v0.3) implements a standardized pipeline event model, already integrated with Argo, Flux, Harbor and demonstrated end-to-end with Argo + Jenkins on Kubernetes. Working groups show scale: 983-member GitOps WG vs 197 in CD Events; vendors (Apple, Fidelity, Netflix) and foundations (OpenSSF, CNCF) are adopting the spec to wire disparate pipelines together and surface realtime triggers without replacing tooling.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:28Community drives GitOps Con EU
- 4:35Open source consensus
- 7:08Modernizing dev workflows
- 11:07CDF and GitOps collaboration
- 16:50Interoperability examples
- 19:39Standardizing collaboration
- 27:06Open source community benefits
- 33:02Getting started in open source
- 36:33Q&A
related talks
06mKeynote: The Future of GitOps
27mGitOps Interoperability with CDEvents: Connecting the Disconnected
06mSponsored Keynote: Argo CD: Bridging GitOps and DevOps
26mKeynote Session: GitOps as an Evolution of Kubernetes
15mKeynote Session: The Difference Between Screwing Around (DevOps) and Science (GitOps) Is Writing It Down
18mKeynote Session: State of the Union: Continuous Delivery Foundation
07mKeynote: Everything as Code: Declarative Application Delivery with GitOps Workflows- Christian Hernandez, Red Hat
47mGitOps and CDevents that helps me get compliant? Really??
