Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Deis @ Docker Randstad 2016

Deis @ Docker Randstad 2016

Deis: PaaS on Kubernetes at Docker Randstad

Gabe Monroy

April 14, 2016
Tweet

More Decks by Gabe Monroy

Other Decks in Technology

Transcript

  1. About Me • Creator and CTO of Deis • Largest

    external contributor to Docker during its formative months • Helped shape operational best practices for CoreOS and etcd
  2. About Deis • Acquired by Engine Yard in April 2015

    • Leading open source PaaS with 5.7 million downloads • Building products for the Kubernetes Ecosystem ◦ Deis Workflow ◦ Deis Helm I have Kubernetes, now what?
  3. 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
  4. 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
  5. Google Cloud Platform kubelet UI kubelet CLI API users master

    nodes etcd kubelet scheduler controllers apiserver The 10,000 Foot View
  6. Why Kubernetes? (for us) • Vibrant community • Declarative APIs

    • Right abstractions • Promotes loose coupling Represents Google’s 10+ years experience with containers at scale
  7. What is Deis Workflow? • Private PaaS running on your

    own infrastructure • Simple developer experience on top of Kubernetes • Force multiplier for operations teams
  8. Deis Workflow for Developers git push deis master deis ps

    deis scale web=5 deis config:set key THING=foo
  9. Why Helm? Should be easy to… • Get up and

    running with common workloads • Define new workloads • Collaborate on workload definitions
  10. 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
  11. 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