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
This document describes the concept of cloning existing CSI Volumes in Kubernetes. Familiarity with [Volumes](/docs/concepts/storage/volumes) is suggested.
25
24
-->
@@ -50,10 +49,10 @@ A Clone is defined as a duplicate of an existing Kubernetes Volume that can be c
The implementation of cloning, from the perspective of the Kubernetes API simply adds the ability to specify an existing unbound PVC as a dataSource during new pvc creation.
52
+
The implementation of cloning, from the perspective of the Kubernetes API, simply adds the ability to specify an existing PVC as a dataSource during new PVC creation. The source PVC must be bound and available (not in use).
54
53
-->
55
54
56
-
从 Kubernetes API 的角度看,克隆的实现只是在创建新的 PVC 时,增加了指定一个现有未绑定 PVC 作为数据源的能力。
Users need to be aware of the following when using this feature:
@@ -69,6 +68,7 @@ Users need to be aware of the following when using this feature:
69
68
* Cloning is only supported within the same Storage Class.
70
69
- Destination volume must be the same storage class as the source
71
70
- Default storage class can be used and storageClassName omitted in the spec
71
+
* Cloning can only be performed between two volumes that use the same VolumeMode setting (if you request a block mode volume, the source MUST also be block mode)
72
72
-->
73
73
74
74
* 克隆支持(`VolumePVCDataSource`)仅适用于 CSI 驱动。
@@ -78,6 +78,7 @@ Users need to be aware of the following when using this feature:
0 commit comments