How to connect postgresql from app using helm and kubernetes?

Question

I am really struggling regarding how my application which is deployed in --dev namespace can connect to postgreSQL database which I deployed independently using helm with --database namespace. What I did so far is as below.

Database and myapp deployed different namespace. I just copy the name PGHOST,PGPASSWORD from some examples but I am not sure where should I use this name and is that has to be same somewhere in postgreSQL?

Should I take care anything else to connect database or is there anything that is not best practice? Should I add a namespace to jdbc url?

Locally we connect to database using below parameters but what should be the way after we deploy our application via helm? We are using sequelize as a client library

const connectionString = postgres://${global.config.database_username}:${global.config.database_password}@${global.config.database_host}:${global.config.database_port}/${global.config.database_name};

postgres values

## Specify PGDATABASE
##
DBName: db

After I deployed postgres;

  # of replicas: 3
  service name:  my-postgres-postgresql-helm
  service port:  64000
  database name: db
  database user: admin
  jdbc url:      jdbc:postgresql://my-postgres-postgresql-helm:port

deployment.yaml

        - name: PGHOST
          valueFrom:
            configMapKeyRef:
              name: {{ .Release.Name }}-configmap
              key: jdbc-url
        - name: PGDATABASE
          value: {{ .Values.postgres.database name | quote }}
        - name: PGPASSWORD
          value: "64000"
        - name: POSTGRES_PASSWORD
          valueFrom:
            secretKeyRef:
              name: {{ template "my-mp.name" . }}
              key: POSTGRES_PASSWORD

configmaps.yaml

apiVersion: v1
kind: ConfigMap
metadata:
    name: {{ .Release.Name }}-configmap
    labels:
        app.kubernetes.io/name: {{ include "my-mp.name" . }}
        app.kubernetes.io/instance: {{ .Release.Name }}
        app.kubernetes.io/managed-by: {{ .Release.Service }}
        helm.sh/chart: {{ include "my-mp.chart" . }}
data:
  jdbc-url: jdbc:postgresql://my-postgres-postgresql-helm..

values.yaml

postgres:
  service name:  my-postgres-postgresql-helm
  service port:  64000
  database name: db
  database user: admin

Amudhan · Accepted Answer · 2020-03-03 13:39:56Z

4

Is this a typo in your question about the jdbc url jdbc url: jdbc:postgresql://my-postgre? You have mentioned that the service name is my-postgres-postgresql-helm and hence the jdbc url should be something like: jdbc:postgresql://my-postgres-postgresql-helm.database. Note the .database appended to the service name! Since your application pod is running in a different namespace, you should append the namespace name at the end of the service name. Had they been in the same namespace, you wouldn't need it.

Now, if that doesn't fix it, to debug the issues, this is what I would do if I were you:

Check if there any NetworkPolicies which add restrictions on the namespace level; that is allowing traffic only between specific namespaces or even pods, which may prevent the traffic from your application pod reaching your postgres pod.
Make sure your Service for postgres pod is proper. That is, describing the service should list the Pod's IP as Endpoints. If not check the Service's label selector and make sure it uses the same labels as the postgres pod.
Exec into your pod and check if your application pod is able to reach the service through nslookup using the service name, that is my-postgres-postgresql-helm.database.

If all these tests are positive and working, then most probably it is some other configuration issue. Let me know if this fixes your issue and GL.

answered Mar 3, 2020 at 13:39

Amudhan

73510 silver badges21 bronze badges

Sign up to request clarification or add additional context in comments.

7 Comments

semural Over a year ago

yes it is a typo.. so the only thing that ı add a namespace at the end of jdbc url? actually my question is also for clarify whether if is everything seems proper in my configuration

Amudhan Over a year ago

You have a postgres pod receiving traffic on a port and a service which exposes that pod. Your application is using the service's hostname (servicename.namespacename) in its configuration to reach the postgres pod. In general this looks like a proper configuration. Check with the namespace name and let me know if it solves.

semural Over a year ago

so my confusion is where should ı make this changes in application? in service.yaml?my-postgres-postgresql-helm-database. So ı thing it has to be something like this at the end

Amudhan Over a year ago

Your app is taking the value from a ConfigMap; the hostname of the postgres db. So just update the configmap to have my-postgres-postgresql-helm.database and things should work fine and that is the right thing to do too.

semural Over a year ago

thanks for your response Amudhan.. actually according to the your response, ı specify a rules in postgres values.yaml as below ingress: - from: - podSelector: matchLabels: app: db . Should ı add this label deployment.yaml and rest of the yamls or deployment.yaml is enough?

|

enkodr · Accepted Answer · 2020-03-03 13:29:34Z

1

If I understand correctly, you have the database and the app in different namespaces and the point of namespaces is to isolate. If you really need to access it, you can use the DNS autogenerated entry servicename.namespace.svc.cluster.local

answered Mar 3, 2020 at 13:29

enkodr

211 bronze badge

Collectives™ on Stack Overflow

How to connect postgresql from app using helm and kubernetes?

postgres values

After I deployed postgres;

deployment.yaml

configmaps.yaml

values.yaml

2 Answers 2

7 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

postgres values

After I deployed postgres;

deployment.yaml

configmaps.yaml

values.yaml

2 Answers 2

7 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related