Building systems on top of complexity doesn't shield anyone from it. The author acknowledges this explicitly: > High Effort - Running anything in Kubernetes is

Building systems on top of complexity doesn't shield anyone from it. The author acknowledges this explicitly: > High Effort - Running anything in Kubernetes is complex, and databases are worse By definition, it's more stuff you need to know. Even if the K8s operator saves time for 95% of the use cases, the last 5% is required. For instance, how do these operators handle upgrading extensions that require on-disk changes? Can you upgrade them concurrently with major version PG upgrades? When the operator doesn't provide a command line admin tool that fits your needs, how do you proceed?