As OpenShift Virtualization adoption continues to accelerate, we are seeing more platform administrators who are NOT familiar with the concept of containers, container images and image registries.  While the process to create a VDDK image is well documented, it still assumes a basic understanding of containerization and also assumes the availability of a container image registry.

The workflow should be made simpler. While the admin will still need to download the VDDK from VMware to stay within licensing constraints, the remainder of the process should be streamlined

What happen:
a. a user must untar the VDDK tar gz
b. a user must build the VDDK container image using YAML
c. a user must push the VDDK container image to quay.io

What should happen:
a. user run automation that untar, build and push the image

Fix:
Use MTV CLI tooling to build the image:
```

1. For example
   oc mtv vddk create --push --tar VMware-vix-disklib-8.0.0-20521017.x86_64.tar.gz --tag quay.io/yaacov/vddk:8.0.0
   ```