Kubernetes Database Operator Ownership Boundaries
A database operator is not a database team in a container. It can reconcile StatefulSets, users, backups, replicas, failover, and certificates. It cannot decide your recovery objective, storage class risk, schema migration policy, or when data loss is acceptable. Those boundaries need to be explicit before production data lands in the cluster. Draw The Ownership Model Write down what each layer owns: database operator -> database cluster lifecycle and reconciliation storage layer -> persistent volume provisioning and attach/mount behavior backup system -> backup storage, retention, and restore mechanics application team -> schema migrations, connection behavior, and query load platform team -> node capacity, security policy, networking, and observability data owner -> RPO/RTO, retention, and data-loss acceptance If every issue is “the operator is broken,” the ownership model is not useful enough. ...