temporalio / temporalio/temporal-worker-controller
Surface "Unhealthy" version in UI / k8s resource info after rollout acceptance test or worker healthcheck fails
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 187
- Forks
- 70
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 31
Description
Open questions:
- How to differentiate between pre-ramp unhealth, ramp unhealth, and general worker health during any version stage.
Contributor guide
No contributing guide indexed for this repository
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
The issue does not name any files, tests, or entry points. First clarify how pre-ramp unhealth, ramp unhealth, and general worker health should differ, then define the UI and Kubernetes resource information that should show an "Unhealthy" version after rollout acceptance or worker healthcheck failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100