Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Continuous Deployment to the Cloud using Spinna...

Andreas Evers
September 19, 2017

Continuous Deployment to the Cloud using Spinnaker - JOIN 2017

In our quest to get to production faster, we've tackled culture, architecture and infrastructure: organizing ourselves in cross-functional DevOps teams, embracing microservice architectures, and deploying to the various clouds out there. Along the way we’ve learned some best practices about how to deploy software at velocity — things like automated releases, immutable infrastructure, gradual rollouts and fast rollbacks.

Andreas Evers

September 19, 2017
Tweet

More Decks by Andreas Evers

Other Decks in Technology

Transcript

  1. Cloud Deployments are Complex Change Change Change Change SVC 1

    SVC 2 SVC 3 Provider A Zone X Provider B Zone Y Provider C Zone Z
  2. 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 images or building containers
  3. Difference with Terraform / CloudFormation Spinnaker strengths lie in it’s

    ability to orchestrate deployment workflows using infrastructure. Terraform [& CloudFormation] shine at the management of cloud primitives. -- Brandon Leach, Lookout
  4. Halyard • Configuration & deployment lifecycle management tool • Install,

    upgrade, configure, validate your Spinnaker installation • Works with Bill of Materials (BOM)
  5. Coming up • Canary strategy • Rolling blue green strategy

    • Declarative CD – config as code • Operational monitoring for Spinnaker