Acces to database from outside in k8s

[CrazyMegaDuck]

Hello!
I have installed postgres operator. How can I get access to postgres database from outside? I tried to change cluster service type from ClusterIP to NodePort, but it is overwritten automatically.

[xzizka]

For testing purposes, you can use port-forward e.g.
kubectl port-forward <service-name> 5432:5432
Have you tried to create a new service instead of editing the one created by postgres-operator?

[FxKu]

With enable_master_load_balancer: true you can change the service to type LoadBalancer. Then it's up to your setup to provide an accessible endpoint.

[CrazyMegaDuck]

For testing purposes, you can use port-forward e.g.
kubectl port-forward <service-name> 5432:5432
Have you tried to create a new service instead of editing the one created by postgres-operator?

Yeah, this is a quick way to test. But I have to give access to all users on the local network.

[CrazyMegaDuck]

With enable_master_load_balancer: true you can change the service to type LoadBalancer. Then it's up to your setup to provide an accessible endpoint.

Thank you very much! It works!

[timmy59100]

@FxKu This works for me but on the master service the selector labels are not created. On the replica service the selector labels are there. So I have to add them myself to access the pod.

Or am I'm doing something wrong here?

selector:
application: spilo
cluster-name: CLUSTERNAME
spilo-role: master

[yanchenko-igor]

@FxKu This works for me but on the master service the selector labels are not created. On the replica service the selector labels are there. So I have to add them myself to access the pod.

Or am I'm doing something wrong here?

selector:
application: spilo
cluster-name: CLUSTERNAME
spilo-role: master

Which version of postgres-operator/spilo are you using? I had the same issue when I upgraded to kubernetes 1.19, but it was solved in the latest versions of postgres-operator/spilo.

[timmy59100]

@yanchenko-igor
Thanks. I'm on Kubernetes 1.19 too. I just updated from spilo-12:1.6-p3 to spilo-12:1.6-p5 but the problem ist persistent.

[yanchenko-igor]

That one is too old, I am using registry.opensource.zalan.do/acid/spilo-cdp-13:2.0-p146 but registry.opensource.zalan.do/acid/spilo-cdp-12:2.0-p144 should be fine too.

[timmy59100]

Ah, I didn't find these. Where are the versions listed?
Updated to registry.opensource.zalan.do/acid/spilo-cdp-13:2.0-p146. But it didn't fix my issue.

[yanchenko-igor]

Service should not be changed, patroni operates with endpoints directly, it should just work.

[timmy59100]

Yes, now I have access to the service.
Thanks!

[timmy59100]

@yanchenko-igor @FxKu
On the main page the image is listed as: registry.opensource.zalan.do/acid/spilo-13:2.0-p2
What is the difference to registry.opensource.zalan.do/acid/spilo-cdp-13:2.0-p146, which should I choose?

Maybe always the latest, which is now registry.opensource.zalan.do/acid/spilo-cdp-13:2.0-p149?

[FxKu]

spilo-13:2.0-p2 is a released version.
spilo-cdp-13:2.0-p149 is the latest dev build. The last release is equivalent to the p147 so there's not a big deviation atm. And I think with some extensions currently updated (Timescale, PostGIS) we will have another release pretty soon.

[tylerrhinehart]

Service should not be changed, patroni operates with endpoints directly, it should just work.

@yanchenko-igor Can you elaborate? What steps or commands do I need to run to expose the service/endpoints outside the cluster?