zalando / zalando/postgres-operator
How to run more than one numberOfInstances with storageClass
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? postgres-operator-1.13.0.tgz
- Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s
- Are you running Postgres Operator in production? no
- Type of issue? question
I'm using https://github.com/zalando/postgres-operator/blob/master/manifests/complete-postgres-manifest.yaml yaml to deploy my cluster on Bare Metal K8s.
Kindly help me define volume and additionalVolumes in this yaml so that I can assign different storageClass to each instance. I eventually want to run numberOfInstances: 2 and want to use different location for each instance. Currently, if I use
volume:
size: 1Gi
storageClass: standard-external
it doesn't support more than one instance as PVCs are not ReadWriteMany enabled.
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 with manifests/complete-postgres-manifest.yaml, focusing on the volume and additionalVolumes settings shown in the issue. Inspect how the operator creates PVCs for numberOfInstances: 2, then confirm whether each instance can receive a distinct storageClass and record the supported configuration or limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100