Spinnaker get control over your deployements
summary
Spinnaker orchestrates CI-driven deployments by picking artifacts from Jenkins/Travis, using a bake stage (Packer-driven VM images or container images) and pushing them through pipelines that use strategies like red/black or rolling canaries with automated metric analysis. It integrates with Kubernetes, AWS ELB/ASG, Eureka and external tools via webhooks (Datadog example). Pipelines decompose into many tasks—typically 15–20 steps and 40–50 API calls—and Halyard handles installation and configuration validation for reliable upgrades and multi-cloud credentials.
AI-written summary · about
chapters (23)
- 0:00Start
- 5:16What Does Spinnaker Mean
- 6:17Kubernetes
- 8:50Service Registries
- 9:54Deployment Strategy
- 10:23Red-Black Deployment Strategy
- 12:52Canary Based Deployment Strategy
- 19:39Live Demo
- 20:47Ui
- 21:48Clusters View
- 25:09Load Balancers
- 28:02Validation Pipeline
- 28:15Bake and Deploy To Test Pipeline
- 29:29Configure Base Images
- 32:35Bake Stage
- 35:29Maximum Number of Server Groups To Leave
- 37:38Custom Strategy
- 38:06Manage Pipeline Templates
- 39:43Halyard
- 42:25Metrics from the Spinnaker Cluster
- 44:05How To Get Started with Spinnaker
- 45:00Stack Overflow
- 47:36Kubernetes Provider
related talks
24mUsing Jenkins and Spinnaker to Supercharge Your Deployment Pipelines
31mHow Spinnaker is Shaping Delivery Excellence at SAP
53mContinuous Deployment with Spinnaker — Automate All Your Deployments!
48mContinuous Delivery with Spinnaker
43mAll Aboard: Transforming Software Delivery Using Spinnaker
22mPractices for Applications Migration to Spinnaker
30mSpinception: Deploying Spinnaker with Spinnaker
19mSpinnaker @ Upside: Getting Started, Establishing Culture & Deploying Microservices with Confidence