Why you shouldn't build a Kubernetes Operator
Operators are Kubernetes agents that know how to deploy, scale, manage, backup, and even upgrade complex, stateful applications. But not every stateful case needs an Operator; from ConfigMaps to StatefulSets, core Kubernetes abstractions overlap with lower-level Operator functionality, and sometimes an application-specific Operator isn’t the right choice. This talk will compare and contrast the Operator pattern with native abstractions to help you know why you shouldn’t (or should) build a Kubernetes Operator.
- Kubernetes abstractions for managing certain kinds of application state: What you don't need an Operator for
- The Operator Framework and SDK: What's still hard about buildling Operators and SDK alternatives
- OLM and version management for dependent applications