Allows overriding the default RollingUpdate via values.strategy — needed
for deployments pinned to a single node by a local-path PVC, where
RollingUpdate can't schedule the surge pod and gets stuck Pending.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0118dTCRPv2onBXbZ3Nb7E2X
Le repo charts.bitnami.com redirige desormais vers repo.broadcom.com et
sert un index.yaml de 27 Mo - le telechargement + parsing depasse
systematiquement les delais internes d'ArgoCD (ARGOCD_EXEC_TIMEOUT et
un timeout interne a helm repo add, ~90s) sur ce reseau homelab (chemin
sortant tres degrade vers ce CDN precis, confirme : <5s en telechargement
direct depuis un autre reseau, >280s et kill depuis le cluster). Vendoriser
les 2 sous-charts (Chart.lock + charts/*.tgz) elimine completement le
besoin d'un appel reseau a chaque sync ArgoCD.
Required since temporal-secret.yaml now validates via required().
Values match the credentials used at initial cluster install.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
NOTES.txt:
- Detect ingress scheme dynamically (http/https based on .Values.ingress.tls)
- Include first path in ingress URL output
- Use .Values.service.port in port-forward example instead of hardcoded 80
- Add -n {{ .Release.Namespace }} to all kubectl commands
postiz-config.yaml:
- Merge temporal enabled/external branches: external address now also emits
TEMPORAL_NAMESPACE and TEMPORAL_TLS, not just TEMPORAL_ADDRESS
temporal-init-job.yaml:
- Use .Values.temporal.postgresql.seeds as PGHOST source (with fallback to
bitnami sub-chart service name) so init job and runtime use the same host
- Switch to quoted heredoc (<<-'SQL') + psql --set to pass credentials as
psql variables, preventing shell expansion from breaking on special chars
temporal-secret.yaml:
- Add required validation: temporal.postgresql.password must be set explicitly
when temporal.enabled=true
values.yaml:
- Remove hardcoded default passwords (postgresPassword, temporal.postgresql.password)
replaced with empty strings to avoid predictable default credentials
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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>
billisdeadandClaude Sonnet 5