Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Modern Applications Web Day | Continuous Delivery to Amazon EKS with Spinnaker

292 Aufrufe

Veröffentlicht am

With more and more application workloads moving to Kubernetes, the interest in managed Kubernetes services in enterprises is increasing. While Amazon EKS will make operations easier, an efficient and transparent delivery pipeline becomes more important than ever. This will provide an increased application development velocity that will directly convert into a competitive advantage with fast paced digital services. While established tools such as Jenkins can be used quite efficiently for CI tasks, modern cloud-native tools like Spinnaker are gaining attention by focusing more in the continuous delivery process. We will show you how Spinnaker and its new Kubernetes v2 provider can be utilized together with Amazon EKS to streamline your application deployments.

Speaker: Jukka Forsgren, nordcloud

Veröffentlicht in: Technologie
  • Loggen Sie sich ein, um Kommentare anzuzeigen.

  • Gehören Sie zu den Ersten, denen das gefällt!

Modern Applications Web Day | Continuous Delivery to Amazon EKS with Spinnaker

  1. 1. AWS - Modern Applications Web Day Jukka Forsgren, Cloud Architect 25-10-2018
  2. 2. About myself
  3. 3. Software deployments in legacy IT - Slow - Fragile - Manual - Bureaucratic
  4. 4. Benefits of a CI/CD pipeline - Automated - Increased velocity - Better developer experience - More productive also for Ops team
  5. 5. Customer project - winter 2018 - Replace old deployment mechanism - Use an established product/project - Provide more visibility and control to developers - Must support all cloud providers - Must support ASG based deployments - Must support containers
  6. 6. Spinnaker - Netflix, Google, Microsoft, Pivotal - Open-sourced in 2015 - Microservices implementation - Part of CNCF landscape
  7. 7. Spinnaker - Supported providers - Google App Engine - AWS - Azure - DC/OS - Docker v2 registry - Google Compute Engine - Kubernetes - OpenStack
  8. 8. Spinnaker - Components - deck (browser based UI) - orca (internal orchestration engine) - igor (integration with Jenkins, Travis CI, etc.) - gate (API gateway) - echo (eventing bus for notifications) - rosco (image bakery) - fiat (authentication service) - front50 (persist all Spinnaker metadata) - kayenta (canary deployments) https://screenshots.firefox.com/1IH Sm9qaD9gGcSVB/www.spinnaker.i o
  9. 9. https://screenshots.firefox.com/1IH Sm9qaD9gGcSVB/www.spinnaker.i o
  10. 10. Spinnaker - Concepts - Account - Application - Cluster - Server group - Pipeline - Stage - Trigger
  11. 11. Spinnaker - Deployment types - Highlander - Red/black - Custom - Rolling red/black (experimental) - Canary (with Kayenta)
  12. 12. Spinnaker - Templated pipelines - YAML - Jinja2 - roer CLI tool - Spinnaker API (gate)
  13. 13. Spinnaker - Installation options - Halyard - Helm Chart - AWS Quickstart
  14. 14. Spinnaker advantages - Tailor made for multi-cloud CD - No need for scripting or plugins - Nice UI into cloud accounts and deployments - Tightly integrated with packer
  15. 15. What’s wrong with Jenkins? - Made before cloud became a thing - Too many plugins - Not designed for containers
  16. 16. Lessons learned - Have OSS mindset - Allocate enough time and resources - Read also armory.io’s documentation
  17. 17. Thank you

×