CSI: make volume creation and snapshot async
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
The CSI volume creation (#10165) and volume snapshot (#10245) workflows are synchronous operations that make the user wait for the response. This was done for implementation expedience -- it's simply easier to wait on the synchronous operation and fail gracefully than it is to implement a deploymentwatcher-like experience. But on some storage providers this can take quite a long time, so it'd be better UX if we had an evaluation-like system for creating volumes and snapshots. The CLI or web UI could then make a blocking query on the progress of that creation, similar to what we'd like to do with deployments.
Related issues:
* Reduce goroutine overhead in `volumewatcher` #9058
* Deployment monitoring during job registration #6818
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the synchronous CSI volume creation issue #10165 and volume snapshot issue #10245, then compare their workflows with the deploymentwatcher-like experience described here. Review related issues #9058 and #6818 for existing constraints. Done means volume and snapshot creation can report progress asynchronously for CLI or web UI clients to query.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100