-
Notifications
You must be signed in to change notification settings - Fork 75
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
support container level snapshot #239
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@umagnus is working on blob directory(container) level volume cloning feature. |
volume cloning feature is supported from v1.23.2, details: https://github.com/kubernetes-sigs/blob-csi-driver/tree/master/deploy/example/cloning |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Is your feature request related to a problem?/Why is this needed
Describe the solution you'd like in detail
Container-level snapshots aren’t currently available. However, you can take blob level snapshots. Blobs now also support versioning, which also work at the blob level.
You can use point in time restore of blobs if you wish to restore all blobs, selected containers or selected blobs in a storage account to a previous point in time.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: