When running a virtualization workload on oVirt, a VM disk is 'natively' a disk somewhere on your network-storage. Entering containers world, on Kubernetes(k8s) or OpenShift, there are many options specifically because the workload can be totally stateless, i.e they are stored on a host supplied disk and can be removed when the container is terminated. The more interesting case is *stateful workloads* i.e apps that persist data (think DBs, web servers/services, etc). k8s/OpenShift designed an API to dynamically provision the container storage (volume in k8s terminology). In this post I want to cover how oVirt can provide volumes for containers running on k8s/OpenShift cluster. Read more @ https://ovirt.org/blog/2018/02/your-container-volumes-served-by-ovirt/