-
Notifications
You must be signed in to change notification settings - Fork 141
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
Restore from SMB file share snapshot feature #136
Comments
…visioned_reclaim_policy test: add e2e test "dynamically_provisioned_reclaim_policy_test"
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. |
/remove-lifecycle rotten |
@andyzhangx, does it make sense to put |
looks like there is still no snapshot restore API: https://docs.microsoft.com/en-us/rest/api/storageservices/snapshot-share cc @RenaShahMSFT any progress on azure file snapshot API v2? |
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. |
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-testing, kubernetes/test-infra and/or fejta. |
@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. |
Currently there is a limitation in Azure SDK and snapshots can only be created, not restored. We don't want users to be able to create snapshots when there is no use for them at this point. Disable snapshots by removing volume snapshot class resource and removing snapshotter sidecars. PR for tracking snapshot restore: kubernetes-sigs/azurefile-csi-driver#136
Currently there is a limitation in Azure SDK and snapshots can only be created, not restored. We don't want users to be able to create snapshots when there is no use for them at this point. Disable snapshots by removing volume snapshot class resource and removing snapshotter sidecars. PR for tracking snapshot restore: kubernetes-sigs/azurefile-csi-driver#136
Currently there is a limitation in Azure SDK and snapshots can only be created, not restored. We don't want users to be able to create snapshots when there is no use for them at this point. Disable snapshots by removing volume snapshot class resource and removing snapshotter sidecars. PR for tracking snapshot restore: kubernetes-sigs/azurefile-csi-driver#136
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Do we know when can we have the support for restore feature? |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
@andyzhangx any news please? |
I apologize if this isn't allowed here. For those looking at alternatives to take Azure Files Snapshot and Restore, the team at CloudCasa.io added native support for it recently. Snapshots are taken using CSI driver, but the Restores are done using native AzureFiles Integration(must provide adequate permissions through an ARM template). It's a work around available through CloudCasa until the CSI driver natively supports this functionality. Hope this helps! https://cloudcasa.io/blog/automating-azure-files-restore-in-aks/ |
@Satsank thanks for the sharing. Do you have more details about |
Hi @andyzhangx, I'm the developer behind automated Azure Files restore and I'll be more than happy to answer the questions. Firstly, there's no need to provide any permissions with an ARM template for Azure Files restore. It's recommended for backing up and restoring AKS clusters infrastructure, but for just Azure Files, it's not mandatory. When it comes to the restore, CloudCasa uses the native Azure SDK to copy the files. Once CloudCasa finds the right snapshot for the PVC, it iterates through the files and copies them one by one to the destination file share. In the case of directories, it recreates the directory and then copies all the files. |
Any updates so far? Was there any progress on the Azure SDK side? Is there some public facing ticket for that SDK that we can track? Thanks |
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 |
/remove-lifecycle stale |
Is your feature request related to a problem?/Why is this needed
Describe the solution you'd like in detail
Currently azure file don't have a restore from snapshot SDK, need to implement that when it's available.
als see ref: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/issues/13#issuecomment-528861659
https://docs.microsoft.com/en-us/azure/backup/restore-afs
https://docs.microsoft.com/en-us/azure/backup/restore-azure-file-share-rest-api
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: