Bring Your Own Artifact Driver To Workflows
summary
Argo Workflows 4.0 adds artifact plugins: you build a containerized gRPC server implementing artifact.proto, push a Docker image, and register it in the workflow-controller ConfigMap while adding it as a sidecar to the Argo server. Plugins run as init container for inputs and as sidecars for saves, implement load/save/delete (delete for GC), can be read‑only, must run non‑root, and have been CI‑exercised (a packaged S3 example exists). Argo server fails to start if registered plugins are unavailable.
AI-written summary · about
chapters (8)
- 0:00Artifact drivers in Argo Workflows
- 3:33Build custom artifact driver plugins
- 7:08Requirements for artifact driver
- 11:46Language for plugin
- 13:53How plugins work under the hood
- 18:28Register plugins with Argo server
- 19:52State and future of artifact drivers
- 21:20Q&A
related talks
05mArgo Workflows 4, What's New And What's Next
20mDemystifying Argo Workflows: An Architectural Deep Dive
30mArgo’s Vibrant Ecosystem and Community
39mBuild and Deploy Your Application with Argo on Kubernetes
36mArgo Workflows: Intro, Update and Deep Dive
23mDemystifying Argo Events: An Architectural Deep Dive
42mArgo Family: GitOps in first class
49mArgo Roadmap Updates For CD, Rollouts, Workflows, and Events