Argo CD Maintainer's Panel
summary
Panel discusses concrete fixes and tradeoffs: how Argo CD externalizes notification secrets (PagerDuty can be pulled from app namespaces), the apps in any namespace feature and steps to split one large app into many without downtime, and when to disable automated sync or use manual preview and sync windows. It covers preview tools: the Argo CD diff preview GitHub Action, GitOps Promoter and the rendered manifest pattern (now beta) plus source-iterator writeback, and why adding new CRDs/controllers increases maintenance burden.
AI-written summary · about
chapters (7)
- 0:00Argo CD maintainers intro
- 1:06Configuring notifications
- 6:04Splitting apps across namespaces
- 10:41Managing config with controllers
- 17:11Preview changes before merge
- 24:12Argo CD migration challenges
- 27:52Closing remarks
related talks
05mProject Lightning Talk: Argo CD at Scale: 5 Features You Should Not Miss!
08mArgo CD Update
25mExtending Argo CD with Health Checks and Resource Actions
30mPanel: What They Don’t Tell You About Shipping Argo CD V3.0: A Maintainer’s...
06mProject Lightning Talk: Argo CD at Scale: 5 Features You Should Not Miss!
18mUnveil the Secret Ingredients for Argo CD in the Enterprise-Scale
35mThe Argo Ecosystem: Tailoring Your Installation Through Community Add-ons
27mExploring Argo