Kubernetes, the container orchestrator created and open-sourced by Google, has emerged as the de facto platform for running applications at scale. At the time of writing, Kubernetes is crossing the chasm from “early adopters” to “early majority” in the hype cycle. Google claims that most of their top cloud customers are using their Kubernetes Engine already. This is not limited to top cloud customers – the reality is that most organizations are either already moving part of their workloads to Kubernetes or planning to do so at some point in the near future.
But how does Kubernetes affect software delivery and operability in large organizations? Although this question cannot be fully answered until Kubernetes reaches a large majority, there are several case studies and anecdotes on the impact of Kubernetes already. Both ops and dev ways of working are impacted, as we will see in this whitepaper.
About the Author
Manuel Pais is an independent DevOps and continuous delivery consultant focused on teams and flow. Manuel helps organizations in the process of adopting DevOps and continuous delivery (both from technical and human perspectives) via strategic assessments, practical workshops, and technical coaching. He’s also the DevOps lead for InfoQ.
Tweets @manupaisable. Blogs @medium.
Manuel Pais and Matthew Skelton curate the widely known DevOps Topologies catalog. A full book on “Team Topologies” is coming out in 2019.