The elephant in the Kubernetes room: Team interactions
Regardless of all the technical benefits that Kubernetes brings, team interactions are still key for successfully delivering and running services. Manuel Pais explores how team design affects the success of Kubernetes adoption.
|Talk Title||The elephant in the Kubernetes room: Team interactions|
|Speakers||Manuel Pais (Independent)|
|Conference||O’Reilly Velocity Conference|
|Conf Tag||Build systems that drive business|
|Date||November 5-7, 2019|
Kubernetes helps tame sprawling microservices architectures and addresses the increased operational complexity. Kubernetes gives developers abstractions and APIs to deploy and run their services. Yet the elephant in the room is that to run, maintain, and evolve the Kubernetes clusters, we need more ops expertise and most likely a dedicated team. Manuel Pais addresses this elephant in the room, raising questions such as whether or not the industry is going back to pre-DevOps isolation between dev and ops teams, if the trade-off between better operational tools and introducing a new dependency layer on the path for applications teams to deliver and run their services worthwhile, and if you’re making life easier for application teams or reducing their end-to-end ownership. Team topologies is a structured approach for thinking about team responsibilities and interactions, which can help you get the most value out of Kubernetes adoption. Manuel draws on research and case studies from the book Team Topologies (Matthew Skelton and Manuel Pais, IT Revolution Press, 2019) with first-hand consulting experience with organizations around the world.