postgres: CloudNativePG vs. hand curated postgres config

https://github.com/cloudnative-pg/cloudnative-pg

- [ ] https://cloudnative-pg.io/blog/building-images-bake
- [ ] https://cloudnative-pg.io/documentation/current/samples/

> ### Mission
>
> CloudNativePG aims to increase PostgreSQL adoption within Kubernetes by making
> it an integral part of the development process and GitOps-driven CI/CD
> automation.
>
> ### Core Principles & Features
>
> Designed by PostgreSQL experts for Kubernetes administrators, CloudNativePG
> follows a Kubernetes-native approach to PostgreSQL primary/standby cluster
> management. Instead of relying on external high-availability tools (like
> Patroni, repmgr, or Stolon), it integrates directly with the Kubernetes API to
> automate database operations that a skilled DBA would perform manually.
>
> Key design decisions include:
>
> - Direct integration with Kubernetes API: The PostgreSQL cluster’s status is
> available directly in the `Cluster` resource, allowing users to inspect it
> via the Kubernetes API.
> - Operator pattern: The operator ensures that the desired PostgreSQL state is
> reconciled automatically, following Kubernetes best practices.
> - Immutable application containers: Updates follow an immutable infrastructure
> model, as explained in
> ["Why EDB Chose Immutable Application Containers"](https://www.enterprisedb.com/blog/why-edb-chose-immutable-application-containers).