zalando / zalando/postgres-operator
Make PostgresContainerName configurable
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hi Ladies and Gents,
Please, answer some short questions which should help us to understand your problem / question better?
- Which image of the operator are you using? ghcr.io/zalando/postgres-operator:v1.10.0
- Where do you run it - cloud or metal? Kubernetes or OpenShift? K8s
- Are you running Postgres Operator in production? yes
- Type of issue? feature request
Currently PostgresContainerName is hard-coded with name postgres :
kubernetes.go
Would it be possible to make it configurable?
Many thanks in advance!
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 reading pkg/util/constants/kubernetes.go, especially the hard-coded PostgresContainerName value. Then trace how this constant is used by the operator and where Kubernetes-related configuration is defined. Done means the container name can be configured without changing the default behavior and the relevant operator tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100