You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+25-23Lines changed: 25 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,6 @@ The volume snapshot feature supports CSI v1.0 and higher. It was introduced as a
6
6
7
7
The volume group snapshot feature supports CSI v1.10.0 and higher, and have been introduced in [Kubernetes 1.27 as an alpha feature](https://kubernetes.io/blog/2023/05/08/kubernetes-1-27-volume-group-snapshot-alpha/).
8
8
9
-
> :warning:**WARNING**: The validation webhook was deprecated in v8.0.0 and it is now removed. The validation webhook would prevent creating multiple default volume snapshot classes and multiple default volume group snapshot classes for the same CSI driver. With the removal of the validation webhook, an error will still be raised when dynamically provisioning a VolumeSnapshot or VolumeGroupSnapshot when multiple default volume snapshot classes or multiple default volume group snapshot classes for the same CSI driver exist.
10
-
11
9
## Overview
12
10
13
11
With the promotion of Volume Snapshot to GA, the feature is enabled by default on standard Kubernetes deployments and cannot be turned off.
@@ -22,15 +20,15 @@ Blog post for the Volume Group Snapshot Alpha feature can be found [here](https:
22
20
23
21
This information reflects the head of this branch.
24
22
25
-
| Minimum CSI Version | Recommended CSI Version | Container Image |[Min K8s Version](https://kubernetes-csi.github.io/docs/kubernetes-compatibility.html#minimum-version)|[Recommended K8s Version](https://kubernetes-csi.github.io/docs/project-policies.html#recommended-version)|
Note: snapshot-controller, csi-snapshotter v4.1 requires v1 snapshot CRDs to be installed, but it serves both v1 and v1beta1 snapshot objects. Storage version is changed from v1beta1 to v1 in 4.1.0 so v1beta1 is deprecated and will be removed in a future release.
29
+
Note: snapshot-controller, snapshot-conversion-webhook, csi-snapshotter v4.1 requires v1 snapshot CRDs to be installed, but it serves both v1 and v1beta1 snapshot objects. Storage version is changed from v1beta1 to v1 in 4.1.0 so v1beta1 is deprecated and will be removed in a future release.
32
30
33
-
Note: when the volume group snapshot feature is enabled, snapshot-controller, csi-snapshotter require the v1alpha1 volumegroupsnapshot CRDs to be installed.
31
+
Note: when the volume group snapshot feature is enabled, snapshot-controller, snapshot-conversion-webhook, csi-snapshotter require the v1beta2 volumegroupsnapshot CRDs to be installed.
34
32
35
33
## Feature Status
36
34
@@ -48,16 +46,17 @@ The CSI external-snapshotter sidecar talks to CSI over socket (/run/csi/socket b
48
46
49
47
In the current release, both v1 and v1beta1 APIs are served while the stored API version is changed from v1beta1 to v1. v1beta1 APIs is deprecated and will be removed in a future release. It is recommended for users to switch to v1 APIs as soon as possible. Any previously created invalid v1beta1 objects have to be deleted before upgrading to version 4.1.
50
48
51
-
### Volume Group Snapshot v1alpha1 APIs
49
+
### Volume Group Snapshot v1beta2 APIs
52
50
53
-
When enabled, the VolumeGroupSnapshot v1alpha1 APIs are being served.
51
+
When enabled, the VolumeGroupSnapshot v1beta2 APIs are being served.
54
52
55
53
## Usage
56
54
57
55
Volume Snapshot feature contains the following components:
58
56
59
57
*[Kubernetes Volume Snapshot and Volume Group Snapshot CRDs](https://github.com/kubernetes-csi/external-snapshotter/tree/master/client/config/crd)
60
58
*[Volume snapshot and volume group snapshot controller](https://github.com/kubernetes-csi/external-snapshotter/tree/master/pkg/common-controller)
59
+
*[Volume group snapshot conversion webhook](https://github.com/kubernetes-csi/external-snapshotter/tree/master/pkg/webhook)
61
60
* CSI Driver along with [CSI Snapshotter sidecar](https://github.com/kubernetes-csi/external-snapshotter/tree/master/pkg/sidecar-controller)
62
61
63
62
The Volume Snapshot feature depends on a volume snapshot controller and the volume snapshot CRDs. Both the controller and the CRDs are independent of any CSI driver. The CSI Snapshotter sidecar must run once per CSI driver. The single snapshot controller deployment works for all CSI drivers in a cluster. With leader election configured, the CSI sidecars and snapshot controller elect one leader per deployment. If deployed with two or more pods and leader election is enabled, the non-leader containers will attempt to get the lease. If the leader container dies, a non-leader will take over.
@@ -66,6 +65,8 @@ Therefore, it is strongly recommended that Kubernetes distributors bundle and de
66
65
67
66
If your Kubernetes distribution does not bundle the snapshot controller, you may manually install these components by executing the following steps. Note that the snapshot controller YAML files in the git repository deploy into the default namespace for system testing purposes. For general use, update the snapshot controller YAMLs with an appropriate namespace prior to installing. For example, on a Vanilla Kubernetes cluster update the namespace from 'default' to 'kube-system' prior to issuing the kubectl create command.
68
67
68
+
There is a new conversion webhook server which provides conversion between v1beta1 and v1beta2 group snapshot objects. The cluster admin or Kubernetes distribution admin should install the webhook alongside the snapshot controllers and CRDs if they want to provide group snapshot v1beta1 API. More details [below](#conversion-webhook).).
69
+
69
70
Install Snapshot and Volume Group Snapshot CRDs:
70
71
* With the repo cloned locally: `kubectl kustomize client/config/crd | kubectl create -f -`
71
72
* From the repo remotely: `kubectl kustomize https://github.com/kubernetes-csi/external-snapshotter/client/config/crd | kubectl create -f -`
@@ -82,23 +83,22 @@ Install CSI Driver:
82
83
* With the repo cloned locally: `kubectl kustomize deploy/kubernetes/csi-snapshotter | kubectl create -f -`
83
84
* From the repo remotely: `kubectl kustomize https://github.com/kubernetes-csi/external-snapshotter/deploy/kubernetes/csi-snapshotter | kubectl create -f -`
84
85
85
-
##### Volume Snapshot
86
+
### Conversion Webhook
87
+
86
88
87
-
* Spec.VolumeSnapshotClassName must not be an empty string or nil on creation
88
-
* Spec.Source.PersistentVolumeClaimName must not be changed on update requests
89
-
* Spec.Source.VolumeSnapshotContentName must not be changed on update requests
89
+
The snapshot conversion webhook is an HTTP callback which responds to
allowing the API server to convert between the VolumeGroupSnapshotContent v1beta1 API to and from the v1beta2 API.
90
92
91
-
##### Volume Snapshot Content
93
+
Read more about how to install the example webhook [here](deploy/kubernetes/webhook-example/README.md).
92
94
93
-
* Spec.VolumeSnapshotRef.Name must not be an empty string on creation
94
-
* Spec.VolumeSnapshotRef.Namespace must not be an empty string on creation
95
-
* Spec.Source.VolumeHandle must not be changed on update requests
96
-
* Spec.Source.SnapshotHandle must not be changed on update requests
97
-
* Spec.SourceVolumeMode must not be changes on update requests
95
+
#### Conversion Webhook Command Line Options
98
96
99
-
##### Volume Snapshot Classes
97
+
*`--tls-cert-file`: File containing the x509 Certificate for HTTPS. (CA cert, if any, concatenated after server cert). Required.
100
98
101
-
* There can only be a single default volume snapshot class for a particular driver.
99
+
*`--tls-private-key-file`: File containing the x509 private key matching --tls-cert-file. Required.
100
+
101
+
*`--port`: Secure port that the webhook listens on (default 443)
102
102
103
103
### Distributed Snapshotting
104
104
@@ -242,6 +242,8 @@ If you have already deployed v1alpha1 snapshot APIs and external-snapshotter sid
242
242
243
243
### Upgrade from v1beta1 to v1
244
244
245
+
Validation webhook should be installed before upgrading to v1. Potential impacts of not installing the validation webhook before upgrading to v1 include being unable to delete invalid snapshot objects. See the section on Validation Webhook for details.
246
+
245
247
* When upgrading to 4.0, change from v1beta1 to v1 is backward compatible because both v1 and v1beta1 are served while the stored API version is still v1beta1. Future releases will switch the stored version to v1 and gradually remove v1beta1 support.
246
248
* When upgrading from 3.x to 4.1, change from v1beta1 to v1 is no longer backward compatible because stored API version is changed to v1 although both v1 and v1beta1 are still served. v1beta1 is deprecated in 4.1.
247
249
* v1beta1 support will be removed in a future release. It is recommended for users to switch to v1 as soon as possible. Any previously created invalid v1beta1 objects have to be deleted before upgrading to version 4.1.
0 commit comments