AMA Spinnaker Roadmap
summary
Roadmap focuses on concrete fixes: a Kubernetes operator with post-install validation that actually runs install and revalidation; tooling and patterns to migrate hundreds of legacy apps into Spinnaker; a Netflix‑backed plugin framework for stages and providers to let teams drop in containerized extensions safely; anonymized community metrics and API autogeneration; managed delivery already in alpha on a few apps and scheduled to expand across Netflix in H1–Q3 2020; plus multi‑location HA and multi‑app visualization work.
AI-written summary · about
chapters (20)
- 0:00Introduction and roadmap context
- 1:21Major community initiatives
- 5:01Installation and operator improvements
- 6:29Application onboarding challenges
- 6:53Plugin framework and ecosystem
- 8:41Netflix’s plugin and extensibility plans
- 10:10API improvements and multi-location support
- 11:37Managed delivery rollout at Netflix
- 13:55Long-term strategic themes
- 15:40Stateful delivery and observability gaps
- 17:55Developer experience and UI focus
- 19:31Legacy system integration needs
- 23:08Plugin architecture and Jenkins comparison
- 26:01Ecosystem partnerships and plugin growth
- 27:26Prioritizing ecosystem requests
- 30:03Multi-cloud abstraction goals
- 32:20Multi-cloud adoption realities
- 34:58Developer engagement and setup challenges
- 36:44Local development integration
- 39:14Q&A session
related talks
28mSpinnaker at Airbnb, one year in
08mSpinnaker as Code SIG Update
36mSpinnaker - Land of a 1000 Builds
34mSpinnaker Technical Oversight Committee Panel
33mPanel Discussion: Spinnaker Success - CD as a Service using Spinnaker
25mEnabling Diverse Application Use Cases using Spinnaker
50mSpinnaker get control over your deployements
18mSpinnaker Summit Opening Keynote