kubernetes / kubernetes/kubernetes
Handle recovery from resize failure
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 128k
- Forks
- 44.6k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 208
Description
Currently when resize fails of a volume it keeps retrying indefinitely. This leads to two problems:
-
Unnecessary API usage for an action that is not going to succeed (for example when you are out of quota on cloud provider or out of bricks on glusterfs).
-
Sometimes user may want to retry volume expansion with lower value. For example - my current PVC is of 12GB and I tried to expand it to 40GB. But that failed. Now I want to retry volume expansion with 20GB except I can’t.
/sig storage
cc @bswartz @saad-ali
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 files, tests, or entry points are named. Start by locating the Kubernetes volume expansion and resize-retry handling, then trace how a failed expansion is retried and how a new lower requested size is processed; done means failed expansions stop retrying indefinitely and a lower retry value can be accepted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100