<div dir="ltr"><div><p style="box-sizing:border-box;margin:0px 0px 8.5pt;color:rgb(51,51,51);font-family:&quot;Source Sans Pro&quot;,&quot;Open Sans&quot;,&quot;Helvetica Neue&quot;,Helvetica,Arial,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">When running a virtualization workload on oVirt, a VM disk is &#39;natively&#39; a disk somewhere on your network-storage.<br style="box-sizing:border-box">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<span> </span><em style="box-sizing:border-box">stateful workloads</em><span> </span>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).</p><p style="box-sizing:border-box;margin:0px 0px 8.5pt;color:rgb(51,51,51);font-family:&quot;Source Sans Pro&quot;,&quot;Open Sans&quot;,&quot;Helvetica Neue&quot;,Helvetica,Arial,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">In this post I want to cover how oVirt can provide volumes for containers running on k8s/OpenShift cluster.<br></p><br></div><div><br></div><div>Read more @ <a href="https://ovirt.org/blog/2018/02/your-container-volumes-served-by-ovirt/">https://ovirt.org/blog/2018/02/your-container-volumes-served-by-ovirt/</a></div><div><br></div></div>