Spinnaker @ Scale for Snap’s Multi Cloud Service Mesh
summary
Snap builds a multi‑cloud service mesh using Kubernetes, Envoy, HAProxy and integrates it with Spinnaker to handle deployments across Google and AWS. A custom provisioning service and switchboard UI generate mesh-aware cluster configs, shrink cluster provisioning from ~2 hours to ~8 minutes, and standardize metrics and canary settings. Current usage shows ~10,000 pipeline runs across ~300 unique pipeline configs and about 170 active developers per month, demonstrating the system works at scale and speeds safe, regional rollouts.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:40Shoutouts
- 1:10The monolithic problem
- 2:34What is a Service Mesh
- 6:40What does it enable
- 7:26Deploying in pipelines
- 8:31Service UI
- 9:25Summary
related talks
50mSpinnaker get control over your deployements
30mSpinnaker as a Platform: Driving Cloud Adoption in Healthcare
17mIntroduction to Spinnaker on Kubernetes
31mEffective building blocks for securing...
05mIgnite – Adrian Todorov
22mPro Tips: Use Spinnaker when Kubernetes multi-tenancy is a nightmare
53mContinuous Deployment with Spinnaker — Automate All Your Deployments!
48mContinuous Delivery with Spinnaker