Thursday, February 18, 2021

PRO SESSION: Why Kubernetes Will Disappear and Why Developers Won’t Care
Join on Hopin
Bruno Andrade
Bruno Andrade, CEO

Should application developers invest the time to learn Kubernetes? Do they even need to be aware of Kubernetes within their infrastructure? It’s become an increasingly popular question that DevOps, platform engineering, and dev teams are asking.

While Kubernetes delivers robust capabilities – far more than most developers need – developers don’t really care about Kubernetes itself. What they care about is delivering their product to users. The arguments in favor of developers learning Kubernetes often revolve around the fact that it’s an incredible tool and well-liked by DevOps. For most developers, these arguments are like being told how fulfilling it is to make your own pizza from scratch, when you have a lot of work to do and would much rather simply order one. Developers only appreciate Kubernetes to the degree that it allows them to focus on doing it faster. They want to eat and not have to cook.

Things can go wrong in the kitchen as well: small changes to Kubernetes have outsized ripple effects. Even experienced developers may find that operators are reluctant to grant them cluster access. The complexity of Kubernetes makes it easy for developers to mess up in unpredictable ways. Because of this, many organizations make years of investments attempting to build a layer between their applications and Kubernetes, in order to abstract Kubernetes away from developers and allow them to simply push code.

Kubernetes needs to transform into a user-friendly application management framework, in the same way Docker turned complex tools such as cgroups into user-friendly products. This session’s audience will learn strategies and tactics for transforming Kubernetes into that user-friendly solution, enabling developers to focus on application code and DevOps and platform engineers to keep control of their clusters and infrastructure.

Takeaways from this presentation will include:

1. How to stop prioritizing Kubernetes, but instead focus more on the applications and the teams that develop and control them.
2. How to stop worrying about ConfigMaps, ingress rules, PVs, PVCs, and other complications in your day-to-day activities.
3. How to enable DevOps and platform engineering teams to move Kubernetes across clusters or even providers without impacting how applications are deployed, operated, and controlled.