[failure mode] revisions that fail to scale up from 0 should set Ready=False
Open
Nobody has claimed this yet.
area/API
kind/spec
triage/accepted
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 1.2k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 2
Description
After a successful initial deploy and scale to zero - if a revision were to fail to scale from 0 a second time we should mark Ready=False.
This intent of this issue is to confirm what is the current behaviour is when readiness & liveness probes fail.
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 source file, test, or entry point is named. Start by tracing revision readiness handling after scale-to-zero and review the existing readiness and liveness probe behavior; done means confirming the current behavior and ensuring a second scale-from-zero failure marks the revision Ready=False.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100