diff options
| author | Rui Cao <ruicao@alauda.io> | 2018-10-16 17:29:31 +0800 |
|---|---|---|
| committer | Rui Cao <ruicao@alauda.io> | 2018-10-16 17:29:31 +0800 |
| commit | c4eef03c552c91351637326be49558f81eb4f142 (patch) | |
| tree | 2842bdb973c1bbc6dec138f99f272ad0547814b6 /contributors | |
| parent | 4655e294feac5e37f07438386f8526ac4d4e82b5 (diff) | |
Typo fix: Kuberentes -> Kubernetes
Signed-off-by: Rui Cao <ruicao@alauda.io>
Diffstat (limited to 'contributors')
| -rw-r--r-- | contributors/design-proposals/storage/data-source.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/storage/data-source.md b/contributors/design-proposals/storage/data-source.md index 80db936b..1cd56caa 100644 --- a/contributors/design-proposals/storage/data-source.md +++ b/contributors/design-proposals/storage/data-source.md @@ -3,7 +3,7 @@ Note: this proposal is part of [Volume Snapshot](https://github.com/kubernetes/community/pull/2335) feature design, and also relevant to recently proposed [Volume Clone](https://github.com/kubernetes/community/pull/2533) feature. ## Goal -Currently in Kuberentes, volume plugin only supports to provision an empty volume. With the new storage features (including [Volume Snapshot](https://github.com/kubernetes/community/pull/2335) and [volume clone](https://github.com/kubernetes/community/pull/2533)) being proposed, there is a need to support data population for volume provisioning. For example, volume can be created from a snapshot source, or volume could be cloned from another volume source. Depending on the sources for creating the volume, there are two scenarios +Currently in Kubernetes, volume plugin only supports to provision an empty volume. With the new storage features (including [Volume Snapshot](https://github.com/kubernetes/community/pull/2335) and [volume clone](https://github.com/kubernetes/community/pull/2533)) being proposed, there is a need to support data population for volume provisioning. For example, volume can be created from a snapshot source, or volume could be cloned from another volume source. Depending on the sources for creating the volume, there are two scenarios 1. Volume provisioner can recognize the source and be able to create the volume from the source directly (e.g., restore snapshot to a volume or clone volume). 2. Volume provisioner does not recognize the volume source, and create an empty volume. Another external component (data populator) could watch the volume creation and implement the logic to populate/import the data to the volume provisioned. Only after data is populated to the volume, the PVC is ready for use. |