From 2b191926d1ea326388b8c9383031d25b8becbb14 Mon Sep 17 00:00:00 2001 From: Raghuram Devarakonda Date: Mon, 23 Sep 2019 11:18:04 -0400 Subject: [PATCH] Volume cloning doc should mention "bound" PVCs. --- content/en/docs/concepts/storage/volume-pvc-datasource.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volume-pvc-datasource.md b/content/en/docs/concepts/storage/volume-pvc-datasource.md index 2cb734b242664..42bdf97460ea1 100644 --- a/content/en/docs/concepts/storage/volume-pvc-datasource.md +++ b/content/en/docs/concepts/storage/volume-pvc-datasource.md @@ -32,7 +32,7 @@ The {{< glossary_tooltip text="CSI" term_id="csi" >}} Volume Cloning feature add A Clone is defined as a duplicate of an existing Kubernetes Volume that can be consumed as any standard Volume would be. The only difference is that upon provisioning, rather than creating a "new" empty Volume, the back end device creates an exact duplicate of the specified Volume. -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. +The implementation of cloning, from the perspective of the Kubernetes API, simply adds the ability to specify an existing bound PVC as a dataSource during new PVC creation. Users need to be aware of the following when using this feature: