Imperative to Declarative: Building a GitOps Driven Unified Control Plane at Autodesk
summary
Autodesk replaces a tangled Jenkins + Spinnaker + homegrown tools matrix with a unified control plane that uses Kubernetes API + CRDs and declarative GitOps, translating existing ADF YAML into CRDs so teams keep the Spinnaker for delivery experience. The claim is faster scaling, stronger compliance, and higher developer productivity; rollout is incremental GitOps rollout starting with low‑risk resources to build trust while avoiding API churn and preserving familiar pipelines.
AI-written summary · about
chapters (8)
- 0:00GitOps control plane intro
- 1:24Developer platform evolution
- 3:30Service oriented architecture benefits
- 5:14Kubernetes as control plane
- 5:35Imperative to declarative challenges
- 8:44Incremental adoption risks
- 10:50GitOps platform benefits
- 11:31Q&A on API translation
related talks
18mKeynote: Faster, Safer, Trusted - The Evolution of Autodesk’s Cloud D...
30mDeclarative by Default, Secure by Design: GitOps as a Control Plane for Governance
40mHow GitOps Changes Everything in CI/CD
47mGitOps - Using Git as your source of truth for build, deploy and observability
07mIntroduction to GitOps
37mSecure Multi-Tenant GitOps Application & Infrastructure Rollouts At Adobe
20mKeynote
05mAgentic GitOps: Evolving Enterprise Delivery