Continuous Delivery for DC/OS with Spinnaker
summary
Cerner extends Spinnaker to deploy to DC/OS, wiring the Spinnaker DC/OS provider to create versioned Marathon apps (server groups), run CI-triggered pipelines, and use metronome run job stages for smoke tests and migrations. Pipelines use expressions, timeouts, execution windows and manual judgment; a destroy stage and find-image-from-cluster promote dev builds to prod. Marathon‑lb proves insufficient so Traffic with a Traffic backend label provides zero‑downtime rollouts; future work targets Edge‑LB API integration.
AI-written summary · about
chapters (24)
- 0:00Intro
- 1:11Why continuous delivery?
- 3:22Safety features
- 5:12Flexible
- 7:34Continuous Delivery Features
- 8:18Multi-cloud
- 9:48Applications and Clusters
- 10:37Server Groups and Instances
- 11:45Marathon applications and tasks
- 13:22Multi-Region Deployments
- 14:09Pipelines
- 15:44Docker Registry Trigger
- 16:42DC/OS Stages Supported
- 18:52Pipeline Expressions
- 20:20Execution Windows
- 21:10Traffic Guards
- 21:54Chaos Monkey
- 23:12Deployment timeouts
- 25:07Incremental Automation
- 25:34Manual Judgment to Rollback
- 26:11Configuration Change Triggers
- 28:10Load Balancer
- 32:20Hello, World!
- 37:54Enterprise and Open Source DC/OS
related talks
36mSpinnaker - Land of a 1000 Builds
52mContinuous Deployment to the Cloud using Spinnaker
48mContinuous Delivery with Spinnaker
50mAdvanced Deployment Strategies and Workflows for Containerized Apps on DC/OS
27mSpinnaker at Salesforce: Enterprise-Level Multi-Substrate Continuous Delivery and Release Management
20mEmpowering Continuous Delivery with Spinnaker: A State of th...
33mPanel Discussion: Spinnaker Success - CD as a Service using Spinnaker
25mEnabling Diverse Application Use Cases using Spinnaker