When temporal.postgresql.user == postgresql.auth.username, the user
already exists with CREATEDB — temporalio/auto-setup handles database
creation itself. The init job only runs for a distinct dedicated user.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Covers 4 scenarios: normal ArgoCD rollback, Gitea outage emergency,
image rollback with/without DB restore, and rollback to a specific Gitea commit.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Covers 4 scenarios: normal ArgoCD rollback, Gitea outage emergency,
image rollback with/without DB restore, and rollback to a specific Gitea commit.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Chart.yaml: bump to version 1.1.0, appVersion v2.21.8
- values.yaml: add temporal section (enabled/address/namespace/tls/apiKey/postgresql),
expand env (~40 non-sensitive vars) and secrets (~60 sensitive vars) to match
current Postiz documentation — covers all social providers, email SMTP,
OAuth OIDC, AI/generation, analytics, MCP, payments, short-link services
- postiz-config.yaml: inject TEMPORAL_ADDRESS (auto-computed or override),
TEMPORAL_NAMESPACE and TEMPORAL_TLS when temporal.enabled or address is set
- temporal-deployment.yaml: temporalio/auto-setup:1.28.1, postgres12 backend,
ES disabled, dynamicconfig volume mount, liveness/readiness probes
- temporal-service.yaml: ClusterIP on port 7233 (gRPC)
- temporal-dynamicconfig.yaml: ConfigMap with development-sql.yaml content
- temporal-init-job.yaml: post-install/upgrade Job that creates the temporal
PostgreSQL user via the postgres superuser before Temporal starts
- temporal-secret.yaml: Secret for temporal PostgreSQL credentials
- NOTES.txt: post-install guidance, search-attribute creation reminder,
multi-replica/local-storage warning, backup reminder
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Add configurable ingress, rename all files to `.yaml` for conformity.
I'm going to merge this as clearly the chart lints, and is installable. Thanks @captainswain for your patience while we fiddle with and fix the CI job.
I'll do some testing offline on one of my Kubernetes clusters to see what sort of a timeout we need to set here on GitHub (that's why the job is still failing).
billisdead
James Read