My predictions in Kubernetes and Platform Engineering for the next 5-7 years 👇🏻
✅ Kubernetes
I spoke to a few colleagues in various roles and based on my research combined with my experience, I believe Kubernetes has a solid 3-4 years left in the tank before it’s just there in the background and no one cares about it.
But then what’s next?
✅ Platform Engineering
I believe in a year or so platform engineering will be in full once it’s actually defined properly.
For example - A lot of folks say that it’s all about creating IDPs, but CNCF says otherwise… so there’s a mix in what it actually is right now.
As Kubernetes continues to gain popularity, engineers have to know how Kubernetes works, and why it might make sense in their environment.
A thread 🧵
Here are a few questions that you should ask yourself
- What benefits does Kubernetes bring to environments?
- What do technologies like containerization do for organizations?
- Does Kubernetes actually help teams?
In this blog post, I’ll provide some basic background on containers and Kubernetes.
Also, some suggestions for how to think about Kubernetes for infrastructure pros.
Are you using Ingress Controllers in your Kubernetes environment?
If not, let's break down what they are.
A thread 🧵
At a high level, Ingress Controllers are:
- Specify multiple paths
- Specify multiple services
All in one load balancer.
Let's break it down.
ingress Controllers are just like any other Controller in a Kubernetes environment. They confirm that the current state is the desired state for the deployment.