Panel: What They Don’t Tell You About Shipping Argo CD V3.0: A Maintainer’s...
summary
Argo CD v3.0 focuses on removing discouraged configs, tightening defaults for security and performance, and avoiding extra maintenance branches by doing a small but mighty release. Community-supplied performance settings (via Slack and Medium) shape defaults. A post-branch cherry-pick adds resource deletion protection after a user accidentally deletes 600 namespaces. Big features like OCI and CLI plugins land in 3.1/3.2 after extra review; GitOps engine reintegrated later to reduce library-maintenance pain. Breaks like label→annotation tracking require explicit upgrade steps.
AI-written summary · about
chapters (17)
- 0:00Argo CD 3.0 panel intro
- 0:42Panel member intros
- 4:15Planning 3.0 with Reggie
- 6:03Coordinating major release
- 7:06Delayed 3.0 features
- 9:14Last-minute feature requests
- 11:02Big features postponed
- 13:08Debates in 3.0
- 15:59Becoming Argo CD maintainer
- 18:27Maintainer approval process
- 19:52Maintainer roles evolution
- 20:35Stability vs innovation
- 22:46Reggie’s release growth
- 24:56Memorable challenges from 3.0
- 25:59Learning from incidents
- 26:59User feedback impact
- 27:20Argo CD 4.0 future
related talks
06mProject Lightning Talk: Argo CD 3.0: What’s New and What’s Next?
08mProject Updates: Argo CD
08mArgo CD Update
28mArgo CD Maintainer's Panel
06mProject Lightning Talk: Argo CD at Scale: 5 Features You Should Not Miss!
05mProject Lightning Talk: Argo CD at Scale: 5 Features You Should Not Miss!
11mArgo Project Velocity Update
49mArgo Roadmap Updates For CD, Rollouts, Workflows, and Events