ArgoCD CLI Gets an Upgrade: Plugins, Flexibility, and More
summary
Adds plugin support to the ArgoCD CLI so any executable named argocd- on the system absolute PATH becomes a subcommand, with the important limitation that plugins cannot override existing subcommands and CLI-level flags reset to defaults for plugins. Demonstrates a real plugin mta (migrate to ArgoCD) that converts Flux HelmReleases and Kustomizations into ArgoCD Application/ApplicationSet CRs and successfully generates apply-ready YAML in the live demo. No SDK yet; list plugins by scanning PATH (ls | grep argocd-).
AI-written summary · about
chapters (14)
- 0:00ArgoCD CLI upgrade intro
- 1:04Kubectl plugin mechanism
- 2:49ArgoCD plugin proposal
- 4:15How plugin commands work
- 6:23Current plugin limits
- 8:29Demo plugin support
- 13:09Custom plugin creation
- 14:10Demo MTA migration
- 18:00Q&A plugin listing
- 20:52Q&A plugin usage
- 21:34Q&A plugin packaging
- 22:38Q&A plugins vs contributions
- 24:03Q&A Flux vs ArgoCD
- 25:07Q&A plugin SDKs
related talks
11mExtending Argo CD CLI Functionality With Plugin Support: Build Your Cust...
29mNextGen Argo: Elevating Continuous Delivery with Easy to Use Plugins
25mExtending Argo Projects: Customizing Argo CD and Argo Rollouts...
08mArgo CD Update
46mFrom FTP to ArgoCD & Argo Rollouts: An adoption history inside a corp
07mLightning Talk: Using Kustomize KRM Functions to Enhance Argo CD Application Deployments
27mExploring Argo
32mIntroduction to ArgoCD
