Before you start
- Persistent storage; one replica
- Configure separate database backups
Configuration that needs your attention
Choose the initial database and user. POSTGRES_USER is the initial superuser; use appropriate application privileges.
Initialization variables apply only to an empty data directory. Changing a stored secret does not rotate an existing database password.
The preset exposes a private SQL endpoint and persists /var/lib/postgresql/data.
Required secrets
Configure these scoped secrets during deployment review in your Hakopod installation. Secret values stay out of the application TOML.
-
database-password
Use this preset
- Open the Catalog in your own Hakopod dashboard and select PostgreSQL.
- Choose the project, environment, and application name. Set the required values and secret references.
- Review the generated configuration, resource requests, networking, and storage plan.
- Deploy, then inspect readiness and logs. Configure backups for persistent data before relying on the service.
Read the upstream setup documentation ↗
View native TOML and setup notes ↗
Pinned container image
docker.io/library/postgres:17.11-alpine@sha256:18cfe3ef5e6815560c98237d6216d1e5119702fb0f3894c8785dd58b8bbe5d73
The catalog pins this image for reproducibility. Review upstream updates and compatibility before changing it.