ai-workspace-infra/gitops
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
704811c14a
gitops/services/database/postgresql
History
Haitao Pan 704811c14a docs(database): rename postgresql tls naming
2026-04-04 08:02:44 +08:00
..
helmrelease.yaml refactor(gitops): consolidate database services and prune legacy assets 2026-04-03 15:52:23 +08:00
initdb-configmap.yaml refactor(gitops): consolidate database services and prune legacy assets 2026-04-03 15:52:23 +08:00
kustomization.yaml refactor(gitops): consolidate database services and prune legacy assets 2026-04-03 15:52:23 +08:00
oci-repository.yaml fix(gitops): point postgresql chart to published tag 2026-04-04 06:54:44 +08:00
README.md docs(database): rename postgresql tls naming 2026-04-04 08:02:44 +08:00
stunnel-client-configmap.yaml refactor(gitops): consolidate database services and prune legacy assets 2026-04-03 15:52:23 +08:00
stunnel-client-deployment.yaml fix(gitops): align postgresql ghcr paths 2026-04-03 21:19:12 +08:00
stunnel-client-service.yaml refactor(gitops): consolidate database services and prune legacy assets 2026-04-03 15:52:23 +08:00
stunnel-server-configmap.yaml refactor(gitops): consolidate database services and prune legacy assets 2026-04-03 15:52:23 +08:00
stunnel-server-deployment.yaml fix(database): align stunnel secret name with tls sync 2026-04-04 07:49:44 +08:00
stunnel-server-service.yaml refactor(gitops): consolidate database services and prune legacy assets 2026-04-03 15:52:23 +08:00
values.yaml fix(gitops): use postgresql auth secret password key 2026-04-04 07:13:22 +08:00

README.md

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-tls.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.