Spinnaker is an open source continuous delivery platform that allows developers to release software changes quickly and safely across multiple cloud platforms. It was originally developed at Netflix to deploy over 100,000 instances to AWS daily using deployment strategies like blue-green deployments and canary releases. The document discusses Spinnaker's architecture, key concepts like pipelines and server groups, and demos how to deploy an application to Kubernetes using a Spinnaker pipeline.

1. Deploywith
Confidence
Spinnaker & Continuous
Deployment
Ethan Rogers
Build & Release Engineer
Skuid

2. AboutMe
• Build & Release @ Skuid
• Spinnaker Contributor
• CI/CD Enthusiast
• @e_frogers (Twitter)
• @ethanfrogers (Slack/Github)

3. AQuickSurvey

4. Overview
• What is Spinnaker?
• Concepts
• Deploying with Spinnaker (Demo!)
• Conclusion

8. WhataboutaCanary?

9. WhataboutRollbacks?

10. WhySpinnaker?
• Safe, repeatable deployments
• Clear picture of what’s running
• Easy scaling and rollbacks
• Multiple deployment strategies OOB
• Consolidated best practices

11. WhatisSpinnaker?

12. Spinnaker is an open source, multi-cloud continuous
delivery platform for releasing software changes with
high velocity and confidence.
- spinnaker.io

14. History
• Developed at Netflix for AWS - 2014
• Open sourced in November 2015
• Lead by Netflix, Google and others

15. Stats
• Netflix runs over 100,000 AWS instances
• Spinnaker deploys 95% of them
• Runs OSS Spinnaker with additional features layered
on top
• 150k pipeline executions (8mil tasks) - Netflix
https://goo.gl/phqX8z

16. Features
• Setup/Admin CLI
• Deployment Strategies
• Email/Chat Notifications
• VM Bakery
• CI Integration
• Chaos Monkey

17. Concepts
• Components
• Server Groups & Clusters
• Pipelines

18. Architecture
• Made up of 9 microservices
• Minimum viable install - 5 services + Redis + S3
• Written in Java/Groovy/Kotlin (Spring)
• github.com/spinnaker/spinnaker

19. • Deck - UI
• Gate - API Gateway
• Clouddriver - Multi-cloud integrator
• Orca -Task orchestrator
• Front50 - Persistent Storage (S3/GCS/Redis)
‣Please don’t use Redis.
Minimum Installation

20. • Igor - Jenkins/Travis integration
• Fiat - Authorization
• Echo - Notifications/CronTriggers
• Rocso - Image Bakery via Packer
• Halyard - Configuration/Installation
Bells &Whistles

22. Instances&ServerGroups
• Instance is a singleVM or Container
• Server Group is group of Instances

23. Instance

24. ServerGroup
chadev-test-v000

25. NamingConvention
• Netflix Frigga
• Used to identify resources
• application-stack-detail-version

26. chadev-test-integration-v001
application stack detail version

27. ServerGroupActions
• Deploy (Create)
• Resize
• Enable/Disable - remove from service
• Clone
• Destroy
• Rollback

28. Clusters
• Logical grouping of Server Groups (enabled/disabled)
• Based on application-stack-detail
• demoapp-staging & demoapp-production

29. chadev-test-v000 chadev-staging-v000
Clusters

30. Applications
• Logical grouping of Clusters
• Based on application-stack-detail
• demoapp
• Multiple environments/regions

31. Applications
chadev-staging-v000 chadev-production-v000chadev-testing-v000

32. Pipelines
• Declarative Deployments
• Multiple trigger sources
• Serial/Parallel stages

34. DemoTime!!

35. • Create a Load Balancer to expose traffic
• Deploy an API service to Kubernetes
• Build a canary pipeline
• Deploy a new version automatically

36. Drawbacks
• Missing good“infra as code”solution
‣ Versioned S3 buckets
‣ https://github.com/spinnaker/dcd-spec
• Can only deploy to cloud based stacks with Docker/VM
• Programatic API access is…difficult
• Built in auditing mechanism

37. CaseStudies
https://goo.gl/tXJoKV https://goo.gl/QcLwhE

38. Reference
• blog.spinnaker.io
• spinnaker.io
• github.com/spinnaker/spinnaker
• http://join.spinnaker.io/

39. We’rehiring!
https://www.skuid.com/careers/