The Case for ArgoCD and CdEvents Integration
summary
Argues Argo CD can both emit and consume cdEvents by wiring the Argo CD notifications controller to produce standardized JSON messages, demonstrated by a handcrafted template YAML and logs showing delivery to the open‑source receiver CD Viz. Shows dashboards correlating service deployed, incident detected and artifact lifecycles across tools, proposes a PR mapping Argo CD fields to the cdEvents spec, and sketches concrete use cases: a universal multi‑instance dashboard, coordinated multi‑service rollback orchestrator, and preview environments triggered by non‑Git events.
AI-written summary · about
chapters (10)
- 0:00ArgoCD and CDEvents intro
- 1:02GitOps dev challenges
- 2:29What are CDEvents
- 4:36CDEvents use cases
- 6:43Adopters of CDEvents
- 7:46ArgoCD emitting CDEvents
- 9:31Demo: ArgoCD to CDViz
- 13:23Advanced ArgoCD/CDEvents
- 17:40Conclusion and next steps
- 19:05Q&A on events
related talks
32mIntroduction to ArgoCD
27mGitOps Interoperability with CDEvents: Connecting the Disconnected
27mExploring Argo
28mArgo CD Maintainer's Panel
23mDemystifying Argo Events: An Architectural Deep Dive
10m#DevOpsSpeakeasy
35mThe Argo Ecosystem: Tailoring Your Installation Through Community Add-ons
04mA Holistic Approach to Software Delivery with Argo
