Atmosphere 2018: Jukka Forsgren - SPINNAKER AND MULTI-CLOUD CI/CD
0 likes35 views
The document discusses Jukka Forsgren's insights on Spinnaker as a multi-cloud continuous deployment (CD) tool, highlighting its advantages over traditional software deployment methods in legacy IT. Key features include orchestration engines, integration with popular platforms, and templated pipelines for streamlined multi-cloud deployments. Lessons learned emphasize the importance of error handling and monitoring during deployment processes.
Atmosphere 2018: Jukka Forsgren - SPINNAKER AND MULTI-CLOUD CI/CD
- 1. Jukka Forsgren Nordcloud Spinnaker and multi-cloud CD
- 2. About myself
- 3. Software deployments in legacy IT ● Slow ● Fragile ● Manual ● Bureaucratic
- 4. ● Increased velocity ● Better developer experience ● More productive also for ops team Benefits of a CI/CD pipeline
- 5. ● Netflix, Google, Waze ● Open-sourced in 2015 ● Microservices implementation ● Part of CNCF landscape Spinnaker
- 7. ● Google App Engine ● AWS ● Azure ● DC/OS ● Docker v2 registry ● Google Compute Engine ● Kubernetes ● OpenStack Spinnaker – supported providers
- 8. ● orca – orchestration engine ● Igor – integration with Jenkins and git ● Gate – API ● Echo – eventing service ● Rosco – image bakery ● Fiat – authentication service ● Front50 – cross-application persistence Spinnaker - components
- 9. ● Account ● Application ● Cluster ● Server group Spinnaker - concepts
- 10. ● Pipeline ● Stage ● Trigger Spinnaker - concepts
- 11. ● Highlander ● Red/black ● Custom ● Rolling red/black (experimental) ● Canary (with Kayenta) Spinnaker – deployment types
- 12. ● YAML ● Jinja2 ● roer CLI tool ● Spinnaker API (gate) Spinnaker – templated pipelines
- 14. ● Halyard ● Helm Chart ● AWS Quickstart Spinnaker - installation
- 15. ● Tailor made for multi-cloud CD ● Provides nice UI into deployments and cloud environments etc. ● Tightly integrated with packer ● No need for scripting or plugins Spinnaker advantages vs Jenkins
- 16. ● Have OSS mindset ● Allocate enough time and resources ● Read also Armory.io’s documentation Lessons learned - general
- 17. ● Error handling/reporting with pipeline templates lacking ● Monitor hal deployment with kubectl ● Monitor pod/container logs for errors and exceptions Lessons learned - technical