The Databases directory contains database operators and the PostgreSQL,
MySQL and MongoDB clusters used by CoRE services.
| Chart | Purpose | Fleet entry point |
|---|---|---|
| Operator | Zalando PostgreSQL and Percona database operators. | Apps/Storage/DBOperator.yaml |
| PSQL | Patroni/PostgreSQL, PGPool, pgAdmin and generated users. | Apps/Storage/PSQL.yaml |
| MySQL | Percona XtraDB Cluster and integrations. | Apps/Storage/Database/MySQL.yaml |
| MongoDB | Percona MongoDB cluster, LDAP/TLS and S3 backup integration. | Apps/Storage/Database/MongoDB.yaml |
ApplicationSets inject cluster, site and environment values. Operators manage database lifecycle; Crossplane user APIs generate identities; ExternalSecret and PushSecret resources synchronize credentials with Vault. Database charts also depend on storage classes, TLS, DNS/networking and S3 backup targets.
Argo CD Synced means only that the operator custom resource matches Git. A
database is healthy only when quorum/replication, storage, backups and client
transactions are healthy.
Before a database change:
- Confirm the selected clusters and the active primary/replica topology.
- Take and verify a recent native backup.
- Check storage capacity, disruption budgets and failure-domain placement.
- Review operator compatibility and upgrade sequencing.
- Verify whether any restore resource will render.
- Change one database/failure domain at a time where practical.
- Validate writes, reads, failover, TLS/LDAP and backups afterward.
Never enable a restore merely to test rendering. Restore objects are executable data operations and must identify an intentionally selected backup.