Overcoming the challenges of using Spinnaker as a multi-tenant CD service
summary
Built a single shared Spinnaker on Kubernetes with centralized config in enterprise GitHub, webhook-driven deployments and a self-service API that reduces onboarding from a week or two to hours or a day. Integrations include Jenkins as a service, Nexus, Vault, Gardener, Grafana and Dynatrace; starter-kit templates (v1 and v2, spin/CLI) automate Helm and canary pipelines. Monitoring, error budgets and Slack alerts drive reliability while permissions and cloud access manager enforce security and separation of concerns.
AI-written summary · about
chapters (11)
- 0:00Start
- 3:38Architecture
- 4:58User Journey for Customers
- 7:17Set Up Central Spinnaker Landscape and Update Its Configuration
- 11:00Sustainability Issue
- 11:47Storytelling
- 12:34Reliability
- 13:29Error Budget Dashboard
- 14:34Workflow
- 16:57Create Business Value
- 17:45Network and Learn
related talks
31mHow Spinnaker is Shaping Delivery Excellence at SAP
45mGetting Started with Spinnaker (part 1)
33mPanel Discussion: Spinnaker Success - CD as a Service using Spinnaker
30mSpinception: Deploying Spinnaker with Spinnaker
50mSpinnaker get control over your deployements
24mUsing Jenkins and Spinnaker to Supercharge Your Deployment Pipelines
32mMaking Spinnaker Your Own
30mSpinnaker as a Platform: Driving Cloud Adoption in Healthcare