zalando / zalando/postgres-operator
UI incorrectly displays clusters with 0 pods
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
It is sometimes desirable to scale down a PG cluster to 0 pods for testing or maintenance. The operator processes such situation normally but the UI gets stuck showing the "Waiting for the 1st container to spawn" message.
It should just display the appropriate warning instead.
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
No file or test is named in the issue. Start by locating the UI code that produces the "Waiting for the 1st container to spawn" message and reproduce a PostgreSQL cluster scaled to zero pods. Done means the UI shows the appropriate warning instead of remaining stuck.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100