zalando / zalando/postgres-operator
Support setting `loadBalancerClass` for loadbalancer services
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? registry.opensource.zalan.do/acid/postgres-operator:v1.11.0 (via helm chart)
- Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K3s
- Are you running Postgres Operator in production? yes
- Type of issue? feature request
We use different kinds of loadbalancers on our cluster, so we need to set spec.loadBalancerClass^1, so the right loadbalancer provider can set the appropriate values. Currently we can only use annotations via replicaServiceAnnotations which issn't enough.
Maybe a generic spec field makes sense, so all kind of service overrides can be used.
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
Start by tracing how the operator creates load balancer Services and how replicaServiceAnnotations is applied, then compare the generated Service with Kubernetes' loadBalancerClass field. The work is done when the field can be configured for the relevant Services and the behavior is covered by the project's existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100