Dallas Spring Connect Presentation by Scott Frederick

1. © Copyright 2018 Pivotal Software, Inc. All rights Reserved. Version 1.0
Continuous Delivery with Spinnaker

2. Scott Frederick
@scottyfred
sfrederick@pivotal.io
Principal Software Engineer on the
Spring engineering team

3. Cover w/ Image
Topics
1. CI and CD
2. Spinnaker Overview
3. Cloud Foundry Integration
4. Concourse Integration

4. Continuous Integration
and
Continuous Delivery

5. Cloud Native
Goals
Ship Faster - Reduce Risk
https://pivotal.io/cloud-native

6. Continuous Delivery
Cloud Native
Goals
Continuous delivery. IT teams make individual software
updates available for release as soon as they are ready.
Organizations that release software rapidly get a tighter
feedback loop and can respond more effectively to customer
needs. Continuous delivery works best with other related
approaches including test-driven development and continuous
integration.
https://pivotal.io/cloud-native

7. Automated Pipelines
Artifact
Repository
Build and
Test
Generate
Artifacts
Source
Code
Repository
Deploy
Runtime
Platform
Runtime
Platform
Runtime
Platform

8. Automated Pipelines
Artifact
Repository
Build and
Test
Generate
Artifacts
Source
Code
Repository
Deploy
Runtime
Platform
Runtime
Platform
Runtime
Platform

9. Focus on fast feedback on every code change
Gives development confidence and security
Allows product owners and business owners to
gauge progress and validate features
Different Goals
Continuous Integration
provides value to the product team
Continuous Delivery
provides value to end users
Focus on getting product in front of users at
planned release intervals
Gives operational confidence and security
Allows product owners and business owners to
get feedback on product features

10. Stateless: Every task runs in its own container,
controlling its own dependencies.
Ephemeral: Clean and consistent builds.
Minimizes test infrastructure to maintain and gives
you flexibility to scale with the cloud.
Traceable: Track versions of external artifacts
used for CI (e.g., git, s3, Docker image). Build
components expressed as code with simple
modeling of modular components.
Flexible workflow automation: Extensible for
compliance or other customized tasks in a
pipeline.
Stateful: Maintains awareness of the topography
(multiple clouds/clusters/foundations), application
inventory, and pipeline activities for compliance
and audit.
Scalable: Performs deployments to multiple
clouds/clusters/foundations with minimal
resources.
Sophisticated deployment scenarios: Canary
deploys, zero-downtime deploys, progressive
deployments (e.g., by time zone),
multi-cloud/foundation deployments.
Opinionated: Built-in best practices for
deployment automation
Different Solutions
CI CD

11. Spinnaker for
Continuous Delivery

12. Spinnaker Is a Continuous Delivery Platform
Spinnaker Community
“...the passionate open source
community dedicated to making
deployment pain go away.”
https://www.spinnaker.io/publications/ebook/

13. Continuous Delivery Foundation
https://cd.foundation

14. Open
Multi-Cloud and Hybrid Cloud

15. Open
Cloud Providers
Amazon Web Services
Cloud Foundry
Google App Engine
Google Compute Engine
Kubernetes
Mesosphere DC/OS
Microsoft Azure
Oracle Cloud
CI Systems
Concourse
Jenkins
Travis CI
Wercker
Artifact Repositories
Amazon S3
Artifactory
Docker
Git
Google Cloud Storage
HTTP
Monitoring
Datadog
Prometheus
Stackdriver
Atlas
SignalFx
(10+ more on
roadmap)
Notifications
Email
HipChat
Slack
SMS via Twilio
Integrations

16. Secure
Authentication
OAuth 2
LDAP
SAML
X.509
Role-based
Authorization
Google Groups
GitHub Teams
LDAP
SAML
Account Secrets Storage
(coming soon)
Git
Hashicorp Vault
CredHub
JDBC
Redis

17. Application Centric Control Plane
=

18. Multi-foundation View

19. Interactive Continuous Delivery Pipeline
CI Arbitrary Jobs

20. Spinnaker Architecture
https://www.spinnaker.io/reference/architecture/
A system of distributed microservices
Each service can be horizontally scaled for HA
and load
All services are configured and deployed using
Halyard
Deployed to Kubernetes for
production use

21. Built-in
CD Best Practices ● Zero-downtime deployments
● Rollbacks
● Automated canary analysis

22. Minimizing Production Deployment Risk
https://www.spinnaker.io/concepts/

23. Multiple Application Versions for Rollback
Allows zero-downtime rollbacks to a set number of previous
application versions without rebuilding the code

24. Automated Canary Analysis
Ensures your applications meet your SLAs
https://medium.com/netflix-techblog/automated-canary-analysis-at-netflix-with-kayenta-3260bc7acc69

25. Spinnaker and
Pivotal Cloud Foundry

26. Spinnaker and
PCF
● Application lifecycle management:
push/destroy/rollback, scale up/down,
enable/disable, map/unmap routes
● Service lifecycle management:
create/update/delete brokered and
user-provided service instances
● Bind applications to services as part of
deployment
● Zero-downtime deployments
● Multi-foundation view of applications
● Manifest-based deployment
● Promotion of applications across environments
● Artifact framework allowing triggering and
assembling deployments out of different parts

27. Spinnaker and
PCF
● Tasks
● Autoscaling
● Container networking configuration
● Optimize installation experience on Pivotal
Container ServiceRoadmap

28. Spinnaker and Concourse

29. Spinnaker and
Concourse
● Modeled after other Spinnaker CI integrations
● Basic auth Spinnaker and Concourse
● Spinnaker trigger and stage
● Concourse resource for stage
● Concourse trigger with build metadata (optional)
○ Concourse resource for build metadata
○ Ability to trigger Spinnaker pipeline
manually and deploy specific Concourse
build

30. Get hands-on with
modern software
October 7–10, 2019
Austin Convention Center
The Reality of Managing Microservice
Deployments at Scale: You Need a Spinnaker
Square Pegs, Square Holes: CI/CD That Fits
Cutting-Edge Continuous Delivery: Automated
Canary Analysis Through Spinnaker

31. Deliver Better Software
All the Time
Continuous Delivery