Cutting-edge Continuous Delivery: Automated Canary Analysis through Spinnaker - CI:CD Meetup Amsterdam 2019

In our quest to get to production faster, we've organised ourselves in cross-functional DevOps teams, embraced microservice architectures, and deployed 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.

One of the most sophisticated techniques of ensuring safety while going fast is called automated canary analysis. While canary deployments are becoming a commodity, having an autonomous judge at your disposal analysing metrics of both baseline and canary deployments, makes all the difference.

Enter Spinnaker, an open-source multi-cloud continuous delivery platform which embodies these core principles of safe, frequent and reliable releases with contributions from Netflix, Google, Microsoft, Oracle and Pivotal.

Transcript

1. © Copyright 2019 Pivotal Software, Inc. All rights Reserved. Cutting-edge Continuous Delivery: Automated Canary Analysis through Spinnaker Fast, Safe, Repeatable Multi-Cloud Deployments
2. Cover w/ Image Who’s this guy? ▪ Andreas Evers - Senior Solutions Architect at Pivotal ▪ Active in Application Transformation (AppTx) EMEA ▪ Used to work for JWorks at Ordina Belgium ▪ @andreasevers on Twitter
3. vSphere Openstack AWS Google Cloud Azure & Azure Stack Shared Services Shared Security Shared Networking Logging & Metrics / Services Brokers / API Management Credhub / UAA / Single Sign On VMware NSX Embedded Operating System (Windows / Linux) Application Code & Frameworks Buildpacks / Spring Boot / Spring Cloud / Steeltoe PAS Pivotal Application Service PKS Pivotal Container Service PFS Pivotal Function Service Pivotal Services Marketplace Pivotal and Partner Products Any App Every Cloud One Platform Concourse PCF 2.0 — for everything that matters
5. Embracing DevOps Culture & Practices
6. Adopting MICROSERVICE Architectures
7. Moving to CLOUD Infrastructure
8. Lessons Learned
9. Deployment Frequency Exploded
10. Change Change Change Change SVC 1 SVC 2 SVC 3 Provider A Zone X Provider B Zone Y Provider C Zone Z Cloud Deployments are Complex
11. Easy Rollbacks are Important
12. Deploy during the Right Timeframes
13. CD Principles
14. 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
15. Deployment Strategies
16. Automation
17. Operational Integration DEPLOY OPERATE
18. Enter Spinnaker
21. App Engine Compute Engine
23. Internal Structure
24. Orca Front50 Spring Boot in the core Gate Clouddriver Rosco Fiat Deck Echo Igor Halyard Kayenta
25. Safer Deploys
26. Rollbacks
27. Deployment Windows
28. Deployment Windows
29. Chaos Monkeys
30. Canary Analysis
31. Canary Analysis
32. More Safety Features ▪ Cluster locking ▪ Traffic guards ▪ Manual judgements ▪ Conditional pipeline & stage execution ▪ Notifications
33. Halyard ▪ Configuration & deployment lifecycle management tool ▪ Install, upgrade, configure, validate your Spinnaker installation ▪ Works with Bill of Materials (BOM)
34. Coming up ▪ Spinnaker CLI for pipelines as code ▪ Declarative CD ▪ More Cloud platforms ▪ Support for “Artifacts” ▪ Comprehensive provisioning support for canary stages ▪ Continue to grow and mature community
36. Demo
37. Demo 34.76.13.187 bit.ly/cdamsterdam
39. © Copyright 2019 Pivotal Software, Inc. All rights Reserved. Slides: https://speakerdeck.com/andreasevers Twitter: twitter.com/andreasevers spinnakerteam.slack.com SO tag:spinnaker spinnaker.io Cutting-edge Continuous Delivery: Automated Canary Analysis through Spinnaker
40. Difference with Terraform / CloudFormation Spinnaker strengths lie in its ability to orchestrate deployment workflows using infrastructure. Terraform [& CloudFormation] shine at the management of cloud primitives. -- Brandon Leach, Lookout