zalando / zalando/postgres-operator
Operator Helm chart should support sidecar configuration
Open
Nobody has claimed this yet.
enhancement
good first issue
- 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.6.2 - Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s
- Are you running Postgres Operator in production? [yes | no] yes
- Type of issue? [Bug report, question, feature request, etc.] feature request
The operator allows configuring sidecars globally so the Helm chart should support it. Will submit a PR for this.
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 does not name specific files or tests. Start by locating the Helm chart's values and templates, then trace how global sidecar configuration is represented in the operator. Done means the chart exposes the sidecar configuration and renders it into the generated Kubernetes resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- databases, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100