Re: Future of the oVirt CSI Driver

On 7/11/23 2:58 AM, Sandro Bonazzola wrote:
I think that if OKD is dropping the oVirt CSI Driver this also will mean nobody will be actively developing it anymore.
I asked about this on the Kubernetes Slack workspace and Vadim mentioned that in order for the OKD project to continue providing oVirt support, someone with oVirt knowledge and operator development would need to step up. It would also require forking the installer and a few other projects, which is something the OKD team spent a lot of effort to not have to do anymore during the 4.x series. https://github.com/openshift/installer Looking at the OpenShift Installer git, so far what's changed is an admin can no longer specify oVirt as a deployment target. According to Jira, there will be a second phase of the deprecation where the actual provisioning pieces (e.g. Terraform) will be removed, but that probably won't be for 4.14. https://issues.redhat.com//browse/OCPBUGS-14818 But not having anyone develop the CSI driver means it will likely end up with bit rot. With OpenShift 4.14 the oVirt platform becomes less attractive to use, though IPI/UPI installations should be possible. A different storage backend would probably be recommended, however. -- Mike Rochefort

On Tue, Jul 11, 2023 at 6:32 PM Mike Rochefort <mroche@omenos.dev> wrote:
But not having anyone develop the CSI driver means it will likely end up with bit rot. With OpenShift 4.14 the oVirt platform becomes less attractive to use, though IPI/UPI installations should be possible. A different storage backend would probably be recommended, however.
OKD can still use oVirt CSI driver as optional component (installable via operator). CSI driver in the payload will, probably, be removed soon anyway -- Cheers, Vadim
participants (2)
-
Mike Rochefort
-
Vadim Rutkovsky