ConfigsApr 16, 2026·3 min read

Spinnaker — Multi-Cloud Continuous Delivery at Scale

Spinnaker is an open-source multi-cloud continuous delivery platform originally built at Netflix, orchestrating safe, high-velocity production deploys across AWS, GCP, Azure, and Kubernetes.

TL;DR
Netflix-born open-source CD platform orchestrating safe deployments across AWS, GCP, Azure, and Kubernetes.
§01

What it is

Spinnaker is an open-source multi-cloud continuous delivery platform originally built at Netflix. It orchestrates safe, high-velocity production deployments across AWS, GCP, Azure, and Kubernetes. Spinnaker provides deployment pipelines with built-in strategies like canary, blue/green, and rolling updates, plus manual approval gates and automated rollbacks.

Platform engineering teams managing deployments across multiple cloud providers or large Kubernetes fleets benefit most from Spinnaker. It is designed for organizations where deployment safety and velocity both matter at scale.

§02

How it saves time or tokens

Spinnaker codifies deployment best practices into reusable pipelines. Instead of writing custom deployment scripts for each service and cloud, teams define pipelines once with baked-in safety features. Automated canary analysis catches regressions before full rollout, preventing costly production incidents. This automation saves the hours spent on manual deployment checklists and rollback procedures.

§03

How to use

  1. Install Halyard (the Spinnaker configuration tool) on a management machine
  2. Configure cloud providers and Kubernetes accounts
  3. Deploy Spinnaker and create deployment pipelines via the web UI
§04

Example

# Install Halyard
curl -O https://raw.githubusercontent.com/spinnaker/halyard/master/install/debian/InstallHalyard.sh
sudo bash InstallHalyard.sh

# Configure Kubernetes provider
hal config provider kubernetes enable
hal config provider kubernetes account add my-k8s \
  --context my-context

# Deploy Spinnaker
hal config deploy edit --type distributed --account-name my-k8s
hal deploy apply

# Access UI at http://localhost:9000 (after port-forward)
§05

Related on TokRepo

§06

Common pitfalls

  • Spinnaker has significant resource requirements (8GB+ RAM for the microservices); underprovisioned clusters lead to instability
  • Halyard configuration is complex; plan for a full day of setup time for a production deployment
  • Spinnaker is overkill for single-cloud, single-service deployments; simpler tools like ArgoCD are better for Kubernetes-only workflows

Frequently Asked Questions

Which cloud providers does Spinnaker support?+

Spinnaker supports AWS (EC2, ECS, Lambda), Google Cloud (GCE, GKE, App Engine), Azure, Kubernetes, Oracle Cloud, and CloudFoundry. You can deploy to multiple providers from a single pipeline.

How does canary deployment work in Spinnaker?+

Spinnaker deploys a canary version alongside the production version and routes a small percentage of traffic to it. Automated canary analysis compares metrics between canary and production. If the canary performs well, Spinnaker promotes it; if not, it rolls back automatically.

Is Spinnaker still actively maintained?+

Yes. Spinnaker is maintained by the Continuous Delivery Foundation (CDF) with contributions from Netflix, Google, and other organizations. It receives regular releases and security updates.

How does Spinnaker compare to ArgoCD?+

ArgoCD focuses on GitOps-style Kubernetes deployments with a simpler architecture. Spinnaker supports multiple cloud providers, has built-in canary analysis, and handles more complex deployment strategies. ArgoCD is simpler; Spinnaker is more feature-rich.

Can I use Spinnaker with a CI tool like Jenkins?+

Yes. Spinnaker is a CD (continuous delivery) tool, not CI. It integrates with Jenkins, GitHub Actions, CircleCI, and other CI tools to trigger deployment pipelines after builds complete.

Citations (3)

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets