cloned volumes - why?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Hey @displague
Why does the plugin clone the volumes when creating backup? why not creating the volume from the snapshot only when running 'velero restore' ?
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 plugin's backup flow and the restore flow described in the issue, focusing on when volumes are cloned and when snapshots are used. Determine the rationale for cloning during backup, then document the decision or define the required change and its restore-time behavior.
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
- 20/100