-
Notifications
You must be signed in to change notification settings - Fork 578
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
[FEATURE] Kubernetes snapshot support (csi-snapshotter) #304
Comments
Any estimates for when the CSI Volume Snapshot is going to be available? |
@lomori csi snapshot support is going to be included in the longhorn 1.1 release which is targeting early November. |
Longhorn longhorn#304 Signed-off-by: Joshua Moody <joshua.moody@rancher.com>
Longhorn longhorn#304 Signed-off-by: Joshua Moody <joshua.moody@rancher.com>
Longhorn #304 Signed-off-by: Joshua Moody <joshua.moody@rancher.com>
Document outlining the kubernetes snapshot support changes between the alpha and beta csi snapshot support. |
Verified on longhorn Master - 09/14/2020 Validation - Pass Executed the test cases from https://rancher.atlassian.net/wiki/spaces/LON/pages/735379688/CSI+Snapshot+Support Once #1788 is closed, we are good to close this feature. |
@khushboo-rancher is this issue good to close? |
Functionality has been validated manually and right now the implementation of integration tests for this feature is in progress. |
@khushboo-rancher thanks no problem you can keep it open then, was just following up :) |
It's unlikely we have time for writing the automation test for this issue in v1.1.0. Let's do a regression test and then punt it to v1.1.1 release. |
Revalidated manually: Pass |
In Kubernetes 1.12, the snapshot support will be added. We will evaluate the feature and if it goes well, we will add the support for it.
The doc is at:
https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/csi-snapshot.md
The external snapshotter:
https://github.com/kubernetes-csi/external-snapshotter
The text was updated successfully, but these errors were encountered: