zalando / zalando/postgres-operator
Possibility of running multiple replicas for postgres-operator pods
Open
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? - v1.10.0
- Where do you run it - AWS EKS
- Are you running Postgres Operator in production? - yes
- Type of issue? - question
Is it possible to run postgres-operator pods deployment more that 1 replica?
Deployment postgres/postgres-operator in chart:
...
spec:
replicas: 2
...
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 the postgres/postgres-operator Deployment in the chart and the v1.10.0 behavior described in this issue. Determine whether setting replicas to 2 is supported on AWS EKS, what limitations apply, and what documentation or implementation change would be needed to make the expected behavior clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100