GitOps Interoperability with CDEvents: Connecting the Disconnected
summary
CDEvents defines a vendor-neutral, structured event format so GitOps tools and enterprise pipelines interoperate instead of brittle glue code. The demo maps ArgoCD events using the notifications controller into CDEvents, sends them to CDViz for dashboards, and shows Flux receiving CDEvents to trigger reconciliations — the pipeline actually produces service_deployed, service_removed and incident events viewable in CDViz. A pull request proposes native ArgoCD mappings and Flux already has receiver support, illustrating standardized delivery telemetry, ArgoCD → CDViz mapping, Flux-driven reconciliations.
AI-written summary · about
chapters (14)
- 0:00GitOps and CDEvents intro
- 1:46Modern GitOps challenges
- 3:56What are CDEvents and why they matter
- 6:05CDEvents workflow
- 8:12CDEvents integration benefits
- 9:59GitOps tools with CDEvents
- 12:29Live demo: Argo CD & CD Viz
- 13:12Argo CD events mapping
- 15:16CD Viz dashboards
- 17:06Flux’s CDEvents support
- 18:09Platform interoperability
- 19:14Argo CD & Flux proposals
- 20:39Enterprise CDEvents use cases
- 22:49Conclusion & CDEvents future
related talks
30mCI/CD Observability: Standardizing with CDEvents
39mKeynote: Bridging The Gap: CDF & GitOps Communities In Collaboration
22mThe Case for ArgoCD and CdEvents Integration
20mEnhancing Interoperability in CI/CD Workflows Using CDEvents
08mBuilding a Future of Greater Interoperability in CI/CD with CDEvents
36mBuilding DevOps Metrics for your Choice of CD Tools Through CDE...
19mAdopting CDEvents and Embracing Interoperability
47mGitOps and CDevents that helps me get compliant? Really??