Spinnaker is an open-source, multi-cloud continuous delivery platform originally built at Netflix. It provides a powerful pipeline management system for safely deploying software to multiple cloud providers including AWS, GCP, Azure, and Kubernetes. This cheat sheet covers Spinnaker's microservices architecture, deployment strategies, automated canary analysis, RBAC, managed delivery, operational patterns, and troubleshooting for teams running Spinnaker in production.
What This Cheat Sheet Covers
This topic spans 18 focused tables and 139 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
Microservices ArchitectureCore Concepts: Applications, Pipelines, and StagesDeployment StrategiesPipeline TriggersArtifact TypesBaking AMIs with RoscoAutomated Canary Analysis (Kayenta)RBAC and Authentication (Fiat)Pipeline Expressions (SpEL)Kubernetes DeploymentMulti-Cloud and AWS Multi-AccountNotifications and ChatOpsCustom and Webhook StagesInstallation and ConfigurationManaged Delivery (Keel)Observability and MonitoringTroubleshooting and Operational RunbooksSpinnaker vs Argo CD Comparison
Microservices Architecture
| Service | Example | Description |
|---|---|---|
http://localhost:9000 | • Browser-based UI • serves React SPA on port 9000 • entry point for all user interactions | |
http://localhost:8084/applications | • API gateway (port 8084) • all external requests route through Gate • handles auth token validation | |
http://localhost:8083 | • Pipeline orchestration engine (port 8083) • manages task and stage execution lifecycle | |
http://localhost:7002 | • Cloud provider interface (port 7002) • caches cloud state and executes mutations (deploy, resize, destroy) | |
http://localhost:8080 | • Metadata persistence (port 8080) • stores pipelines, applications, projects, notifications | |
http://localhost:8088 | • CI integration bridge (port 8088) • polls Jenkins, GitHub, Travis CI • propagates build events to Echo |