Argo CD - Plugins as Services
summary
Argues that decoupling Argo CD config management plugins from the repo server into external services enables independent scaling, safer service-account isolation, easier installation via a Helm chart install, and better observability. Uses gRPC-based gRPC discovery with plugins advertising a listen on port 880 and a plugin.yaml for capabilities. Demonstrates converting an existing Helmfile plugin by adding a small Dockerfile and listen address; works but increases repo transfer latency and requires network-based discovery and additional service read permissions.
AI-written summary · about
chapters (8)
- 0:00Introduction to Argo CD
- 0:49Config management plugins
- 3:30Architecture shift
- 4:25Benefits of the service model
- 5:57Development and scaling
- 7:20Trade-offs and advantages
- 11:02Implementing plugins as services
- 13:02Future outlook and community
related talks
27mBuilding a Better Software Supply Chain
29mKubernetes Reloaded AKA How to Avoid the Dev Plateau with CRDs
10mDo We Need Yet Another CD Tool?
32mThe HashiCorp Packer Plugin Repository, What’s init?
23mBuild plugins using Pluggy
31mExtensibility without chaos: lessons from building Cozystack
27mArchitecting for Change Debate
53mChange your tools, change your outcome