From af208b37c11f43a98f056f4f042f836684f101fb Mon Sep 17 00:00:00 2001 From: Mariusz Mazur Date: Thu, 14 Feb 2019 16:52:15 +0100 Subject: [PATCH] Typo --- doc/datavolumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/datavolumes.md b/doc/datavolumes.md index 440b62a9a..6d8fd6393 100644 --- a/doc/datavolumes.md +++ b/doc/datavolumes.md @@ -3,7 +3,7 @@ ## Introduction Data Volumes(DV) are an abstraction on top of Persistent Volume Claims(PVC) and the Containerized Data Importer(CDI). The DV will monitor and orchestrate the upload/import of the data into the PVC. Once the process is completed, the DV will be in a consistent state that allow consumers to make certain assumptions about the DV in order to progress their own orchestration. -Why is this an improvement over simply looking at the state annotation created and managed by CDI? Data Volumes provide a versioned API that other project like Kubevirt](https://github.com/kubevirt/kubevirt) can integrate with. This way those project can rely on an API staying the same for a particular version and have guarantees about what that API will look like. Any changes to the API will result in a new version of the API. +Why is this an improvement over simply looking at the state annotation created and managed by CDI? Data Volumes provide a versioned API that other project like [Kubevirt](https://github.com/kubevirt/kubevirt) can integrate with. This way those project can rely on an API staying the same for a particular version and have guarantees about what that API will look like. Any changes to the API will result in a new version of the API. ### Status phases The following statuses are possible.