ArgoCD deployment fails due to PostgreSQL serviceBindings incompatibility:: The orchestrator chart uses the PostgreSQL chart's `serviceBindings` functionality to share database credentials. The PostgreSQL chart implements this feature using Helm `lookup()` function, which is not supported by ArgoCD server-side rendering. This prevents successful deployment when using ArgoCD. As a consequence, ArgoCD deployments fail with password authentication errors, database creation jobs fail silently, and SonataFlow services cannot connect to PostgreSQL. As a work to deploy with ArgoCD, complete the following steps: . Disable `serviceBindings` in your configuration: + [source,yaml] ----   upstream:     postgresql:       serviceBindings:         enabled: false ---- . Create a pre-existing secret with the name `<release-name>-postgresql-svcbind-postgres` containing the following content: + [source,yaml,subs="+attributes,+quotes"] ----   apiVersion: v1   kind: Secret   metadata:     name: <release-name>-postgresql-svcbind-postgres   type: Opaque   data:     username: <base64-encoded-username> # e.g., "postgres"     password: <base64-encoded-password>     postgres-password: <base64-encoded-password> # Same as password ---- . Configure the chart to use the existing secret: + [source,yaml,subs="+attributes,+quotes"] ----   upstream:     postgresql:       auth:         existingSecret: <release-name>-postgresql-svcbind-postgres         secretKeys:           adminPasswordKey: password ----