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

DoxLON Feb 2019 - To Kube or not to Kube?

Vik Bhatti
February 12, 2019

DoxLON Feb 2019 - To Kube or not to Kube?

With all the hype and community around Kubernetes right now its hard to ignore the project, but are all problems really kube-shaped? In this talk I will dive into some of the things that can go wrong with a poorly designed Kubernetes installation, and why Trussle is moving away from it in 2019.

Vik Bhatti

February 12, 2019
Tweet

More Decks by Vik Bhatti

Other Decks in Technology

Transcript

  1. To kube or not to kube? Vik Bhatti Head of

    Infrastructure @otaku_coder
  2. Running opensource software at scale “Debugging open source software that’s

    built with technology unfamiliar to you but you’re running in production is like performing life saving exploratory surgery on an extraterrestrial being that crash landed in your back yard.” Jameson Lopp CTO @CasaHODL https://twitter.com/lopp/status/1093518751830556672
  3. The Infrastructure Story 2016 First 2 engineers hired Decided on

    AWS + Elastic beanstalk CodeShip - because it was free 2017 Teething pains with Elastic Beanstalk Hired first QA - moved to Jenkins Hired first infra engineer - moves to k8s k8s on AWS deployed with KOPS Lots of regular outages + frustration 2018
  4. Kubernetes - Why we struggled Kube the easy kinda hard

    way Run by an inexperienced team Manual undocumented tweaks Frustrating developer experience Too many turtles!
  5. The Startup Cloud Journey Early product experiments Builds + deployments

    Continuous Delivery Infrastructure- as-code Automate everything Microservices Testing/QA Early stage Seed/Series A Growth Scale Lots of change Chaos Engineering Basic infrastructure Data Infrastructure Low Cost/ High Risk High Cost/ Low Risk
  6. Infrastructure Roadmap Migrate from k8s to ECS New multi-account architecture

    (using terraform) Establishing continuous delivery + automation Coaching teams on AWS