[K8S-STAND-PGSQL] Bad DB_CONNECTION_URI generated about infisical HOT 2 CLOSED

Hi back!

I think I can say "My bad" because today after re-installing the chart there were no problems at all ...
I don't know why my instances couldn't connect to the Postgresql included in the helm chart.

I was not aware that the /etc/resolv.conf was filled automatically

We can close this issue since it was more a setup problem than a chart problem.

Thanks for your time!

from infisical.

Hey @AurelienConte ! It's indeed a good practice to define the entire FQDN if ever you move services between namespaces (doesnt happen that often) or just to be sure to point to the right one.

Although, the kubelet automatically configure a /etc/resolf.conf in each pod for it to be able to resolve any hosts in the same namespace, so the current helm template works as expected.

$ cat /etc/resolv.conf 
search my-service.svc.cluster.local svc.cluster.local cluster.local my-namespace
nameserver 10.32.0.10
options ndots:5

If you want to point to a different postgresql instance (managed externally) you can configure it in the DB_CONNECTION_URI variable in the infisical-secrets k8s secret used by the infisical pod to get default/extra configs.

However, I don't understand why your instance isn't starting, it should.. Do you have any useful logs? Are you sure it's related to the DB_CONNECTION_URI?

Hope it helps

from infisical.