I know, I know. I hate Kubernetes. Why am I talking about it so much? Because it’s a great technology to expose the challenges that most organizations face. Kubernetes was designed to host stateless processes. If Netflix needs a surge in video encoders or streamers, Kubernetes orchestrates the provisioning of thousands of container instances almost instantly. When demand has subsided, those instances disappear.
Traditional enterprise applications aren’t designed to operate in that fashion. For example, application servers in legacy design keep some type of configuration state in the application server. If you’ve ever had to load balance across a set of application servers that wanted to “own” the application session, you’ll understand why you can’t simply containerize application server of a 3-tier monolithic app.
So, what if you do have a bunch of stateless application components you’d like to containerize and adopt cloud-native operations to those systems? I sat down with Damani Corbin to talk about where I believe the gaps are in Kubernetes maturity and what Damani has seen in his travels as a Kubernetes expert helping companies deploy Kubernetes at scale.
I hope you enjoy this fun and insightful conversation.