Pod is not deleted when workspace pod status gets Error
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Bug description
When the workspace pod is an error (i.e., .status.phase == "Failed"), the workspace remains undeleted.
internal link
This is probably due to the fact that the finalizer is not erased. Because we have succeeded in clearing the Error pod by erasing the finalizer.
Steps to reproduce
we don't know. But there is the one example
Workspace affected
No response
Expected behavior
If a pod gets Error status, it will be deleted properly.
Example repository
No response
Anything else?
No response
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 TypeScript workspace-pod cleanup path for pods whose status.phase is "Failed", focusing on finalizer handling; the issue names no files or tests. Use the reported example to reproduce the failure if available, then verify that an Error pod is deleted and its finalizer is cleared.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, typescript
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100