Available in editions:  Ultimate/EE, SE+

Included in extensions: On-prem IaaS

The module lifecycle stage: General Availability

The cloud-provider-zvirt module integrates Deckhouse Platform with zVirt. It allows the node-manager module to use zVirt resources when provisioning nodes for a NodeGroup.

The module is automatically enabled for all cloud clusters deployed in zVirt.

Features of the cloud-provider-zvirt module:

  • Managing zVirt resources via cloud-controller-manager, which updates Kubernetes node addresses and removes from Kubernetes the nodes whose virtual machines no longer exist in zVirt.
  • Provisioning disks via the zVirt CSI driver (csi.ovirt.org) and creating StorageClasses for zVirt storage domains so that PersistentVolumes can be requested from the cluster.
  • Provisioning CloudPermanent nodes using the Terraform/OpenTofu provider terraform-provider-ovirt.
  • Provisioning CloudEphemeral nodes via Cluster API (CAPI). Virtual machine parameters are set in the ZvirtInstanceClass resource.
  • Registering with node-manager so that ZvirtInstanceClass can be used when describing a NodeGroup.
  • Enabling CNI for new clusters automatically. By default, cni-cilium is used.

If the cluster was installed with the ZvirtClusterConfiguration schema, it must be migrated to the ModuleConfig-based configuration. Until the migration is complete, the D8CloudProviderZvirtMigrationPending alert may fire and Deckhouse Platform updates may be blocked.

The migration procedure is described in “How to migrate a cloud provider to ModuleConfig-based configuration?”.

Third-party components

List of third-party software used in the cloud-provider-zvirt module:

  • zVirt CSI driver release-4.22

    License: Apache License 2.0

    CSI driver for zVirt (OpenShift oVirt CSI driver).

  • zVirt Terraform provider 2.2.0

    License: BSD 3-Clause License

    Terraform provider for zVirt (oVirt).