Source: thenewstack.io
Kubernetes: When to Use, and When to Avoid, the Operator PatternCategory: Software, Database, Security, Data, Kubernetes, automation, yaml, ansible
In the world of Kubernetes, Operators have quickly become a popular pattern far beyond their initial use for encoding deep operational knowledge about running stateful applications and services like Prometheus. But the complexities of CRD lifecycle management they bring with them means that writing an operator will not always be the best solution for your own applications, because you’re creating more code to maintain.
One option is that you can just run jobs or use existing components and of tie them together, instead of building operator that would do the same thing.
Because writing operators commits you to maintain the code, you will also have to commit to hiring more developers and a Kubernetes platform team who have skills with operators in the future, to make sure you use of Kubernetes is robust and secure.
If you do decide you need to write operators to do what you need, “You should really think about having something that reduces privileges for the duration that the operator is idle,” Naor suggested.
One option is that you can just run jobs or use existing components and of tie them together, instead of building operator that would do the same thing.
Because writing operators commits you to maintain the code, you will also have to commit to hiring more developers and a Kubernetes platform team who have skills with operators in the future, to make sure you use of Kubernetes is robust and secure.
If you do decide you need to write operators to do what you need, “You should really think about having something that reduces privileges for the duration that the operator is idle,” Naor suggested.
Related Articles
Community Partners
DevOps Careers