Hey everybody! In this post, I’d like to talk about Container-centric infrastructure with Kubernetes. This is Part 1 of a series of posts on using installing and using Kubernetes.
Let’s start with the kubernetes documentation.
Before containers, we installed applications directly on the target host, along with libraries our apps needed, plus the libraries any other applications needed as well.
At best, it presents DevOps with maintenance challenges. And at worst, integration conflicts between applications, versions of dependent libraries, and so on, can lead to poor application performance and even downtime.
With containers, on the other hand, all the applications run in their own isolated mini environments, away from each other, and the underlying OS.
And this is what you get with Kubernetes!
Container-centric infrastructure like that provided by Kubernetes has tremendous benefits, and in Part 2 I’ll give you an overview of Kubernetes, and talk about Pods, Nodes, and the “desired state” of the cluster. Stay tuned for that.
Want to know more?
Check out this video at IBM developerWorks TV, where I show you everything I covered in Parts 1-5 of this series:
Thanks for reading!