Natalia Marukovich

Postgres on Kubernetes usually works well enough — until the operator itself becomes part of the incident. The harder problems tend to show up in two areas that operator documentation rarely covers: troubleshooting incidents that cross multiple systems, and sizing the operator pod and its reconciliation behaviour.

Database operators automate many database operations, but they do not automate database ownership. Failover, backups, certificate rotation, and consistent deployment are handled well. The line between what the operator covers and what your team still owns is less visible — and it usually...