A Reality Check About Cloud Native DevOps

We were trying to deploy real apps for clients; complicated, messy things which don’t look like a conference slide, and we had a ton of questions:

  • Should we build our own cluster or use a managed Kubernetes service?
  • How big should the cluster be?
  • How should we deploy app updates to the cluster?
  • How do we configure replicas, shared volumes, load balancers, databases, IP addresses, DNS records, and all those fun things, and update them along with the app using infrastructure as code?
  • How do we set up the cluster and the app to be secure?
  • How do we integrate all this with our CI systems?
  • Which of the zillion Kubernetes add-on tools are actually helpful? How should we use them?
  • DevOps and infrastructure engineers who are responsible for operating applications in production, at scale, and who want to know where Kubernetes fits into this, what it can do for them and how to get the best out of it;
  • Developers who don’t have a dedicated ops team, but who need to deploy their apps to the cloud and run them reliably, scalably, without having to be an infrastructure genius. Kubernetes is great for this;
  • CTOs, engineering managers and tech leads who want to know the business angles: how is Kubernetes going to benefit my company? How is it going to help us ship working software faster, to more customers, with fewer defects, with lower fixed costs and better flexibility? What arguments will help sell the idea of adopting Kubernetes to my management?

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Semaphore

Semaphore

Supporting developers with insights and tutorials on delivering good software. · https://semaphoreci.com