The Evolution of Cuberns Operators

In cubidetes, an operator acts almost like a person on your team in charge of keeping these things, or keeping your services and pods. And so when you need a change to your services, you ask the operator to do it by changing their definition of resources. This is where operators came from; they are responsible for publishing this api that is in charge of kind of running things and making changes. The flow went from operators triggering manual actions with no automation, to operators writing system specific automations, moving to internally maintained system specific automation, and finally ending up atonomous systems that need no human intervention.