postgres-operator icon indicating copy to clipboard operation
postgres-operator copied to clipboard

Custom cluster port not working when i update my cluster

Open vhartmannselfee opened this issue 10 months ago • 2 comments

Please, answer some short questions which should help us to understand your problem / question better?

  • Which image of the operator are you using? e.g. ghcr.io/zalando/postgres-operator:v1.14.0
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? Kubernetes in OVH Cloud
  • Are you running Postgres Operator in production? yes
  • **Type of issue? Bug

Hello,

On a cluster i put : spec.postgresql.parameters.port = 1646

My cluster is accessible and it give service on 1646,

But when i update this cluster zalando postgres operator try to communicate with cluster on port 5432 instead of 1676 and update failed.

I need to temporary modify cluster service port to update it,

Thanks for your help

vhartmannselfee avatar Jan 27 '25 13:01 vhartmannselfee

I'm pretty sure we hard code the standard postgres port 5432 here and there - so configuring the port via the manifest is expected to break things. Why do you need it?

FxKu avatar Feb 14 '25 15:02 FxKu

Hello, I want the port not to be 5432 to prevent malicious bots from detecting that the IP concerns a postgre SQL server

vhartmannselfee avatar Mar 03 '25 10:03 vhartmannselfee