While waiting for this to be approved I also tested this in my production environment. Works as intended.

Hey @mpsOxygen, you should already be able to do this when you disable the in cluster Postgres and set your own postgres connection URL via DB_CONNECTION_URI. An example is shown in step 4 here https://infisical.com/docs/self-hosting/deployment-options/kubernetes-helm. Is this helpful?

https://github.com/Infisical/infisical/blob/main/helm-charts/infisical-standalone-postgres/templates/infisical.yaml#L67

Hello @maidul98,

I know about kubeSecretRef: "infisical-secrets", but I now realize I did not explain my use case correctly.

I use an operator to take care of postgres. When it spins up a postgres cluster for me, it creates a secret with all needed information (db name, user, pass, uri, etc). The password for example is randomly generated each time a cluster is spun up. Or it maybe even changes. The operator takes care of everything and puts it in a secret it creates and manages. All I need from my apps is to say: get your DB_CONNECTION_URI from the secret the operator created. So while I know about the secret that gives infisical it's ENVs, using it would mean to manually update it every time something changes. This patch fixes my problem because I just tell infisical the name of the secret the postgres operator uses to keep postgres connection info.