Skip to main content
EARLY ACCESS

This feature is available as Early Access (EA) and should not be used in production.

System Requirements

Before enabling Portworx Fusion Controller, ensure that your cluster meets the following requirements:

  • Have Portworx Enterprise version 3.6.0 or later installed.
  • Have Operator version 26.1.0 or later installed.
  • Have Portworx CSI version 26.1.1 or later installed.
  • Supports deployment of KubeVirt VMs.
  • Run OpenShift version 4.18.7 or later.
  • A Fusion Coordinator endpoint and valid LDAP credentials for the Coordinator available.

Limitations​

Enabling Portworx Fusion Controller in your Portworx cluster includes the following limitations:

  • Supports creating KubeVirt VMs only using data volume templates.
  • Does not support attaching an existing PersistentVolumeClaim to a VM.
  • Does not support hot-plugging volumes into running VMs.
  • Does not support an ActiveCluster setup.
  • Does not support secure multi-tenancy (realms).
  • Does not support FlashArray pods.
  • Does not support using different Fusion preset (that is, the different Fusion-backed StorageClass) for different disks in the same VM. All disks within a VM must reference the same StorageClass.
  • When adding a new disk to an existing VM, the disk must use the same Fusion-backed StorageClass as the existing disks. If you attempt to use a different StorageClass, the operation is rejected.
  • Fusion-backed StorageClass objects are not supported for use with container workloads such as Deployments or StatefulSets.
  • In mixed deployments that use both Fusion-managed and non-Fusion volumes, Portworx Fusion Controller supports only the storage protocols that are already configured and available. Portworx Fusion Controller does not extend or modify protocol support in such environments.
Last updated on