Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

cloned volumes - why?

Open
#5 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go, kubernetes

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.

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' ?

Dominant language
Go
Stars
6
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linode/velero-plugin

All issues in linode/velero-plugin

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.