zalando / zalando/postgres-operator
Log that operator is waiting for master to become healthy/available
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Due to config the wrong label reflected that master pod is there but from logs it was hard to figure out that operator was waiting for another label to be present.
Log every 30 seconds or every 60 seconds what the worker is still waiting for pod with "spilo_role_label" label.
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
Locate the operator worker logic that waits for a pod with the "spilo_role_label" label and review its existing logging. Add periodic messages identifying what the worker is waiting for, then verify that the logs distinguish a present master pod from a healthy or available master.】【。
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100