zalando / zalando/postgres-operator
Custom cluster port not working when i update my cluster
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Reproduce a Kubernetes cluster update with spec.postgresql.parameters.port set to 1646, compare the operator's connection port with the service port, and define done as a successful update without temporarily changing the service port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100