Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Custom cluster port not working when i update my cluster #2855

Open
vhartmannselfee opened this issue Jan 27, 2025 · 2 comments
Open

Custom cluster port not working when i update my cluster #2855

vhartmannselfee opened this issue Jan 27, 2025 · 2 comments
Labels

Comments

@vhartmannselfee
Copy link

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

@FxKu
Copy link
Member

FxKu commented Feb 14, 2025

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 FxKu added the question label Feb 14, 2025
@vhartmannselfee
Copy link
Author

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

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants