-
Notifications
You must be signed in to change notification settings - Fork 547
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
doc: lift snapshot creation/deletion and new volume creation support to Beta #2304
Conversation
Cloning and restoring from snapshot with thick-provisioning enabled need a newer Ceph version. Older versions did not copy zero-filled contents, but made the volumes thin-provisioned. Is that something that should be noted somewhere? |
@nixpanic good point.. I think we can keep a seperate entry for thick provisioning cloning and restoring in the matrix and mark existing ones as thin provisioned . wdyt? |
or keep a diclaimer under the fields we have in the matrix and add a note below the matrix about this, that can also be done. |
@nixpanic as discussed , we will add a seperate section for non CSI spec specific features in a seperate matrix. With that in mind, this is good to go, ptal . Thanks 👍 |
Since kubernetes 1.17 snapshot functionality is at Beta state and external snapshotter 3.0.3. Since v4.0.0 of snapshotter controller and kubernetes v1.20, the snapshot functionality has been lifted to GA. Ceph CSI drivers have been supporting this feature for last few releases and users are heavily using this feature since then. We also have good amount of e2e test case which cover volume creation from snapshot backend or iow, snapshot as a datasource. With that, this PR proposes of lifting this feature support to Beta with v3.4.0 version. Updates# ceph#2199 Signed-off-by: Humble Chirammal <[email protected]>
Since kubernetes 1.17 snapshot functionality is at Beta state and external snapshotter 3.0.3. Since v4.0.0 of snapshotter controller and kubernetes v1.20, the snapshot functionality has been lifted to GA. Ceph CSI drivers have been supporting this feature for last few releases and users are heavily using this feature since then. We also have good amount of e2e test case which cover volume creation from snapshot backend or iow, snapshot as a datasource. With that, this PR proposes of lifting this feature support to Beta with v3.4.0 version. Updates# ceph#2199 Signed-off-by: Humble Chirammal <[email protected]>
Since kubernetes 1.16 clone ( create a new volume from exisiing volume) functionality is at Beta state and kubernetes v1.18, the snapshot functionality has been lifted to GA. Ceph CSI drivers have been supporting this feature for last few releases and users are heavily using this feature since then. We also have good amount of e2e test case which cover volume creation from PVC backend or iow, PVC as a datasource. With that, this PR proposes of lifting this feature support to Beta with v3.4.0 version. Signed-off-by: Humble Chirammal <[email protected]>
Since kubernetes 1.17 snapshot functionality is at Beta state
and external snapshotter 3.0.3. Since v4.0.0 of snapshotter controller
and kubernetes v1.20, the snapshot functionality has been lifted to GA.
Ceph CSI drivers have been supporting this feature for last few releases
and users are heavily using this feature since then.
We also have good amount of e2e test case which cover snapshot creation
and deletion and other operations on the same. With that, this PR
proposes of lifting this feature support to Beta with v3.4.0 version.
This PR also lift clone functionality to Beta stage
Updates: #2199
Signed-off-by: Humble Chirammal [email protected]