Add support for Volume snapshot for CloudStack CSI driver #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
Testing performed:
Snapshot Creation
Logs in CSI controller:
Snapshot Deletion
logs in the csi-controller container
Snapshot restore - by creating a new Pod
Created PVC from snapshot
Then created a Pod that used the PVC
As seen the PVC is bound to a Persistent Volume (volume on CloudStack:
pvc-6e1fc165-563b-4036-bfda-42138b97a284
)Pod with volume created from snapshot is in Running state
Logs of successful volume creation from snapshot and attach to the worker node (additional logs added for debugging purpose)
Tested at Project level
Requires upstream changes to allow snapshot APIs for the kube-admin role
Logs indicating that volume was successfully created from snapshot and attached to the node:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.