Continuous Deployment

to the Cloud using

Spinnaker

Moving to

CLOUDInfrastructure

EMBRACING

DevOpsCULTURE & PRACTICES

ADOPTING

MICROSERVIC

EArchitectures

Lessons Learned

Deployment Frequency Exploded

Cloud Deployments are Complex

Change

Change

Change

Change

SVC 1

SVC 2

SVC 3

Provider AZone X

Provider BZone Y

Provider CZone Z

Easy Rollbacks are Important

Deploy during the Right Timeframes

CD Principles

Immutable Infrastructure

• We want the process of building, testing, deploying and

validating to be as deterministic as possible

• We want repeatability and predictability across environments

• Through baking/building images

Deployment Strategies

Automation

Operational Integration

DEPLOY OPERATE

Enter Spinnaker

Container Engine App Engine

Compute Engine

Internal Structure

Orca

Front50

Spring Boot at its core

Gate

Clouddriver

Rosc

o

Fiat

Deck

Echo

Igor

Halyard

Useful Features

Halyard

• Configuration & deployment lifecycle management tool

• Install, upgrade, configure, validate your Spinnaker installation

• Works with Bill of Materials (BOM)

Planning

Planning

Chaos Monkey

Canary Analysis

Difference withTerraform / CloudFormation

Spinnaker’s strengths lay in its ability to orchestrate

deployment workflows with infrastructure.

Terraform [& CloudFormation] shine at the management of

cloud primitives.

-- Brandon Leach, Lookout

Coming up

• Canary strategy

• Rolling blue green strategy

• Declarative CD – config as code

• Operational monitoring for Spinnaker