27 lines
967 B
Markdown
27 lines
967 B
Markdown
# PostgreSQL GitOps Bootstrap
|
|
|
|
This stack uses ExternalSecrets to materialize runtime credentials from Vault.
|
|
The GitOps manifests intentionally do not store secret values.
|
|
|
|
## Vault paths expected by this stack
|
|
|
|
- `postgresql.svc.plus`
|
|
- `POSTGRES_USER`
|
|
- `POSTGRES_PASSWORD`
|
|
- `GHCR_USERNAME`
|
|
- `GHCR_TOKEN`
|
|
## Bootstrap rule
|
|
|
|
Before or during initial reconciliation, the Vault key `postgresql.svc.plus`
|
|
must be seeded with the runtime credentials expected by the manifests in this
|
|
directory. Otherwise the ExternalSecrets controller will report
|
|
`Secret does not exist`.
|
|
|
|
## Helper
|
|
|
|
Use `scripts/seed-vault-postgresql.sh` from a trusted admin shell to write the
|
|
expected Vault keys from local environment variables or existing K8s Secrets.
|
|
The shared TLS Secret for `postgresql-vultr.svc.plus` is synchronized by the
|
|
`k3s-platform` Helm chart into `database/postgresql-tls`, which
|
|
`stunnel-server` consumes directly. Do not commit the secret values to Git.
|