baddental.blogg.se

If your cluster does not come pre-installed with the correct components, you may manually install these components by executing the following steps.

Kubernetes distributors should bundle and deploy the controller and CRDs as part of their Kubernetes cluster management process (independent of any CSI Driver). The snapshot controller will be creating the VolumeSnapshotContent CRD object which triggers the CSI external-snapshotter sidecar to create a snapshot on the storage system.įor detailed snapshot beta design changes, see the design doc here.įor detailed information about volume snapshot and restore functionality, see Volume Snapshot & Restore.įor detailed information (binary parameters, RBAC rules, etc.), see. The CSI external-snapshotter sidecar only watches the Kubernetes API server for VolumeSnapshotContent CRD objects. The snapshot controller will be watching the Kubernetes API server for VolumeSnapshot and VolumeSnapshotContent CRD objects. sig-storage/snapshot-controller:v2.1.4įor more information on the CSI external-snapshotter sidecar, see this external-snapshotter page. Snapshots take the disk, memory, and device state of a guest virtual machine at a specified point in time, and save it for future use. Unsupported Versions Latest stable release See the following table for snapshot-controller release information. When Volume Snapshot is promoted to Beta in Kubernetes 1.17, the CSI external-snapshotter sidecar controller is split into two controllers: a snapshot-controller and a CSI external-snapshotter sidecar.

Versioning, Support, Compatibility Policies