Skip to content
deepak gupta edited this page Feb 15, 2021 · 5 revisions

Welcome to the Working-with-spinnaker-study wiki!

Spinnaker Introduction

Spinnaker is a continuous delivery tool that helps you be intentional about how you ship software by granting visibility & control into your software delivery process. Specifically, Spinnaker is an open source, multicloud, continuous delivery platform

Spinnaker Pipelines

Delivering an application with Spinnaker requires a pipeline. This pipeline can be reused and iterated on as your needs change.

Spinnaker Deployment Strategies

To automate deployments and get code to production faster.Spinnaker supports several deployment strategies: Blue/Green, Rolling Blue/Green, Highlander, and Canary.

Blue/Green: You have two instances of your deployment running concurrently, the production build and a new one. Once you feel confident or certain criteria are met, traffic shifts all at once from the old deployment to the new one. A configurable number of server groups are maintained with the old production build, allowing for easy, fast rollback.

Rolling Blue/Green: Similar to Blue/Green, but traffic is gradually shifted from the older deployment to the new one.

Highlander: Similar to Blue/Green, except the old deployment is destroyed once traffic is shifted.

Canary: Three instances: production, a baseline instance (a smaller clone of production), and a canary instance with the new deployment. Production handles most of the load while the baseline and canary each receive a smaller amount. After a predetermined amount of time, performance of the baseline and canary are compared. The new deployment becomes the new production build if requirements are met. The canary analysis can be automated or manual.