Getting Started With Spinnaker (part 2)
summary
Shows how to turn a UI pipeline into a reusable export pipeline template JSON, add template variables for account and namespace, and generate per-service pipelines. Describes two delivery models: template-based self service and git-backed sync using spin API to keep pipeline JSON in a repo. Covers permissions: accounts versus applications versus pipeline roles and service accounts plus dynamic accounts in 1.16. Explains deployment strategies including red black and blue green with traffic managed via replica sets, and risk control with automated analysis of metrics and logs.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker intro
- 1:16Pipeline templates for enterprises
- 5:10Rollback and deployment strategies
- 10:10Creating templates from pipelines
- 17:00Self-service pipelines from templates
- 22:16Git-sync pipeline management
- 23:21Spinnaker permission models
- 27:23Traffic management strategies
- 29:54Canary deployments and analysis
- 36:50Blue-green deployment insights
- 38:41Automated verification benefits
- 41:16Testing and verification workflow
- 42:51Multi-cloud and future features
related talks
18mOvercoming the challenges of using Spinnaker as a multi-tenant CD service
31mHow Spinnaker is Shaping Delivery Excellence at SAP
19mSpinnaker @ Upside: Getting Started, Establishing Culture & Deploying Microservices with Confidence
50mSpinnaker get control over your deployements
25mEnabling Diverse Application Use Cases using Spinnaker
28mScale CI/CD in Your Enterprise Through An Internal Spinnaker as-a-Service Model
23mBuild a Spinnaker pipeline in highly regulated bank environment
33mPanel Discussion: Spinnaker Success - CD as a Service using Spinnaker