Deis @ Kubernetes Berlin

Introduction to Deis, CNCF, Kubernetes, Deis Workflow and Helm from the Kubernetes Berlin meetup in May 2016. Live demo not included ;)

Transcript

1. Kubernetes Berlin
2. About Deis • Acquired by Engine Yard in April 2015 • Leading open source PaaS with 6.3 million downloads • Building products for the Kubernetes Ecosystem ◦ Deis Workflow ◦ Deis Helm I have Kubernetes, now what?
3. Accelerate the transformation to cloud native computing
4. Empower Developers • Create applications • Deploy code or Docker images • Configure runtime environment • Manage releases and rollbacks • Run administrative commands • View aggregated logs • Scale out via the process model • Collaborate with a team … with simple, easy-to-use CLIs and APIs
5. Empower Operators Cloud Native Operational Model Infrastructure Ops Cluster Ops Application Ops
6. Cloud Native
7. Cloud Native Computing Foundation Source: https://cncf.io/
8. What is a Cloud Native Application? 1. Container packaged 2. Dynamically scheduled 3. Microservice based
9. CNCF: Scope Source: https://docs.google.com/presentation/d/11kp272oeNxpvNTZVYMoH5LsdrLRXIm2PTD5DrVjYFZs/edit#slide=id.gd6a2cee48_23_49
10. CNCF: Composite Microservices Source: https://docs.google.com/presentation/d/11kp272oeNxpvNTZVYMoH5LsdrLRXIm2PTD5DrVjYFZs/edit#slide=id.geba7160b9_10_113
11. CNCF: Publication & Deployment CI/CD drives immutable infrastructure • components are replaced not modified • images are baked on demand Deployment services use monitoring data to canary, roll forward, roll back Changes propagate through dependency graphs automatically subject to policy Source: https://docs.google.com/presentation/d/11kp272oeNxpvNTZVYMoH5LsdrLRXIm2PTD5DrVjYFZs/edit#slide=id.geba7160b9_10_120
12. CNCF: Technologies The initial focus of the Cloud Native Computing Foundation will be integrating the orchestration layer of the container ecosystem. Joyent, CoreOS, IBM, VMWare, Cisco, Weaveworks and others have all offered up relevant technology and we look forward to working closely as a group to bring the disparate projects together cleanly. Kubernetes has been offered as a seed technology. Source: https://docs.google.com/presentation/d/11kp272oeNxpvNTZVYMoH5LsdrLRXIm2PTD5DrVjYFZs/edit#slide=id.gd6a2cee48_23_49
13. Kubernetes
14. What is Kubernetes? Greek for “Helmsman”; also the root of the words “governor” and “cybernetic” • Runs and manages containers • Inspired and informed by Google’s experiences and internal systems • Supports multiple cloud and bare-metal environments • Supports multiple container runtimes • 100% Open source, written in Go Manage applications, not machines
15. Google Cloud Platform kubelet UI kubelet CLI API users master nodes etcd kubelet scheduler controllers apiserver The 10,000 Foot View
16. Google Cloud Platform UI API Container Cluster All You Really Care About
17. and 1000s more... Kubernetes Real World Adoption
18. Why Kubernetes? (for us) • Vibrant community • Declarative APIs • Right abstractions • Promotes loose coupling Represents Google’s 10+ years experience with containers at scale
19. Using Kubernetes is really complicated
20. Deis Workflow
21. What is Deis Workflow? • Private PaaS running on your own infrastructure • Simple developer experience on top of Kubernetes • Force multiplier for operations teams
23. Deis Workflow for Developers git push deis master deis ps deis scale web=5 deis config:set key THING=foo
24. Deis Workflow for Operators kubectl helm
25. Deis Helm
26. The best way to find, share and use software built for Kubernetes
27. Why Helm? Should be easy to… • Get up and running with common workloads • Define new workloads • Collaborate on workload definitions
28. Helm vs. Workflow • Workflow focused on 12-factor applications • Helm focused on non-12-factor applications ◦ Databases ◦ Queues ◦ Caches • Helm promotes a Kubernetes-native approach • Helm is a tool for operators, not developers Helm is used to install Workflow
29. Demo
30. Road to Workflow 2.0 • Beta 1 ◦ Released March 25, 2016 • Theme: Operator UX ➔ Beta 2 ◦ Target April 13, 2016 • Theme: Stability ➔ Beta 3 ◦ Target April 27, 2016 • Theme: Monitoring ➔ Beta 4 ◦ Target May 11, 2016 • Release Candidate ◦ Target May 25, 2016 • Deis Workflow Stable ➔ June 8, 2016
31. Workflow 2.1 Deis Doctor Teams and Permissions Service Broker
33. Questions?