Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cloned volumes - why? #5

Open
mzimry opened this issue Feb 11, 2024 · 2 comments
Open

cloned volumes - why? #5

mzimry opened this issue Feb 11, 2024 · 2 comments

Comments

@mzimry
Copy link

mzimry commented Feb 11, 2024

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

@displague
Copy link
Collaborator

displague commented Feb 11, 2024

Hi, @mzimry.

I've created:

It looks like you walked down a similar path with you comment here: linode/linode-blockstorage-csi-driver#107 (comment)

This project clones the volume because this is functionally equivalent to taking a snapshot (short of support for an snapshot feature and any benefits or optimizations that may come with that approach). This is the simplest way to ensure that an off-cluster clone of the volume exists.

I don't see API alternatives: https://www.linode.com/docs/api/volumes/#volume-clone (there is no volume-snapshot feature, not an object to create a bucket from a blockstorage volume)

@displague
Copy link
Collaborator

I am so disconnected from this project that I completely forgot Linode Object Storage was involved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants