I made a [**short video**](https://youtu.be/ha3LjlD6g7g) explaining what Kubernetes operators are and why this operator concept even emerged.
Operators are used mainly for stateful applications. So I first compare how Kubernetes manages stateless and stateful applications. And then compare deploying and managing stateful applications without an operator compared to deploying it with a Kubernetes Operator.
A short overview:
► **1. StateLESS applications on Kubernetes**
Kubernetes can manage the complete lifecycle of stateless applications in a fully automated way, because these applications don’t have business logic for deployment.
**► 2. StateFUL applications WITHOUT Operator**
On the other hand stateful applications, like databases, need more "hand-holding" during its whole lifecycle, because the replicas of stateful apps aren't identical.
Kubernetes natively doesn’t have all the knowledge required to automate the process of deploying every single stateful application. That’s why these kind of applications require manual intervention - people who "operate" these applications.
**► 3. StateFUL applications WITH Operator**
Operator solves this problem and basically replaces this "human" operator with a "software" operator.
Hope this video will be helpful for you 🙂
3 thoughts on “Heard about Kubernetes Operators, but don’t know exactly what they are and why they are useful? 🤷🏻♂️”
Super awesome video, thanks!
Some people think it is part of kubernetes, but it’s not!
They use inbuilt mechanisms, but they are built outside of the kubernetes dsl.
Haha, when I first saw the title I was preparing to respond with your video. Your content is great!