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.

Sign up for GitHub

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

Jump to bottom

Investigate Volume Cloning #207

Open
leakingtapan opened this issue Feb 11, 2019 · 29 comments
Open

Investigate Volume Cloning #207

leakingtapan opened this issue Feb 11, 2019 · 29 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone
0.7

Comments

@leakingtapan
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Volume Cloning and creating a new volume from existing volume is a feature supported by CSI 1.0. We should investigate whether it is beneficial to EBS

Describe the solution you'd like in detail
TBD
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 12, 2019
@leakingtapan
Copy link
Contributor Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 13, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 11, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 10, 2019
@leakingtapan
Copy link
Contributor Author

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Sep 11, 2019
@leakingtapan
Copy link
Contributor Author

/remove-lifecycle stale

@leakingtapan leakingtapan added this to the 0.6 milestone Sep 27, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 26, 2019
@leakingtapan
Copy link
Contributor Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 8, 2020
@MrNorm
Copy link

MrNorm commented Apr 2, 2020

+1

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 1, 2020
@frittentheke
Copy link
Contributor

+1

1 similar comment
@ArseniiPetrovich
Copy link

+1

@frittentheke
Copy link
Contributor

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 19, 2020
@leakingtapan leakingtapan modified the milestones: 0.6, 0.7 Aug 9, 2020
@ognots
Copy link

ognots commented Oct 10, 2020

+1

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 8, 2021
@ayberk
Copy link
Contributor

ayberk commented Jan 8, 2021

/remove-lifecycle stale
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 8, 2021
@Jaybe-bdk
Copy link

+1

1 similar comment
@phewitt
Copy link

phewitt commented Mar 17, 2021

+1

@hdiass
Copy link

hdiass commented Apr 14, 2021

Is VolumeCloning something you guys support or not ?

@wongma7 wongma7 mentioned this issue Jun 4, 2021
Closed
@Tishka17
Copy link

I am also interested in CSI Volume Cloning feature. Is it supported or not?

@nariman-maad
Copy link

@vishal-swarankar-sdl
Copy link

I am also interested in CSI Volume Cloning feature. Is it supported or not?

@torredil
Copy link
Member

Currently, EBS doesn't support volume cloning. The driver can add support for cloning if/when EBS adds support for this.

bertinatto pushed a commit to bertinatto/aws-ebs-csi-driver that referenced this issue Sep 23, 2022
@openshift-merge-robot
Merge pull request kubernetes-sigs#207 from gnufied/fix-older-dockerfile
430a06d 
Fix older dockerfile
@HarryWeppner
Copy link

@torredil, do you know the state of EBS volume cloning in 2023?

@ksliu58
Copy link

ksliu58 commented May 1, 2023

Thank you for your interest. For copying volumes, we recommend that customers take a snapshot of their volume and create a new volume (the copy) from that snapshot. Can you provide details on your use case for volume cloning?

@FriedCircuits
Copy link

FriedCircuits commented Feb 20, 2024 •
edited
Loading

@ksliu58 I could of using this feature today to restore a PV for our Jenkins deployment. I was redoing some stuff on the Jenkins helm chart and storageClass and wanted it to reattach to the previous volume. I could of quickly use this to create a new PVC from the existing one so it would be attached to this helm deployment. I used the work around and created a volume snapshot of the existing volume and use that with dataSource restore, but takes longer having to wait for AWS to create the snapshot etc.

@AndrewSirenko
Copy link
Contributor

/priority important-longterm

@k8s-ci-robot k8s-ci-robot added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Feb 26, 2024
@roma-glushko
Copy link

It would be nice to support this to simplify the EBS volume cloning workflow.

Imagine there is some user-facing functionality where there is an entity that has a dedicated volume. Users may want to duplicate an entity which would entail duplication of the underlying volume.

Doing the duplication via a temporary snapshot would definitely work but it's not the most simple way I guess. Also, in terms of cloning latency, if EBS CSI supported the K8S CSI cloning, would it work any faster than the "take snapshot -> create a new volume with a dataSource pointed to the snapshot" workflow?

@JobRamos
Copy link

Tried to perform this feature on EKS v1.29 but it is still unavailable, receiveing the message ProvisioningFailed "CSI driver does not support clone operations: controller CLONE_VOLUME capability is not reported".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
0.7
Development

No branches or pull requests