zalando / zalando/postgres-operator
Improve bootstrap: don't wait for all replicas until users are created
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
The first pod and master is quickly available and then the operator currently continues to wait until the remaining pods in the statefulset also are healthy and have the replica label attached. As this adds additional wait time for the user and creates a window where the database is available but no users for employees or application are created the operator should start with role and database creation once the first pod with the master label is available.
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 the operator's bootstrap flow from StatefulSet readiness and the master label through role and database creation. Verify the current wait condition and how user creation is triggered. Done means role and database creation starts when the first master-labeled pod is available, without waiting for all replicas to become healthy and labeled.
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
- 35/100