The container orchestrator landscape

Personally the operator concept in k8s is a HUGE thing for me.
It allows me to deliver ALL users of standard apps, such as databases (postgresql, mongodb etc.) and other type of services, which can be very complicated to deliver in a scalable and highly-availalble manner, while enabling me to ensure that backup and recovery is HANDLED - and I need only have ONE set of procedures/documentation for handling this - and it works for ALL users of this (as we then use this operator for ALL places where we need f.ex. postgresql).

It saves me and my colleagues soo much time - and actually gives a huge pease of mind, knowing that our growing infrastructure - its not beyond us, to actually do a recovery test, we have a decent chance at believing will work for all services we operate. And we're a small company.. I've consulted for many larger corps - and k8s to me, enables the delivery of a "pre-determined but flexible enough" solution, to enable automatic consumption of "operations services" - by development teams - where the ops team has an actual chance of ensuring the ops quality is maintained.

As opposed to the old world of just handing out VMs and really "hoping for the best and otherwise blaming the developer teams".

It is defeintely complex though, and you should definetely be aware of your choices and their cost in complexity.