System Requirements

This section includes detailed system requirements to ensure a seamless deployment and optimal performance of Portworx CSI in your Kubernetes environment. Portworx CSI requires a cluster with a minimum of three nodes. All nodes and backend storage systems must meet the following specifications:

Hardware requirements

Category	Requirement
CPU	1 CPU
RAM	2 GB minimum
Operating System Root Partition	Minimum: 64 GB Recommended: 128 GB
Network Connectivity	Bandwidth: Recommended: 10 Gbps Minimum: 1 Gbps
Node Type	Bare metal or virtual machine (VM)

Purity version requirements

Ensure that the Pure Storage FlashArray and FlashBlade are running the required Purity version:

FlashArray

Installation type	Minimum Purity version required
FlashArray without secure multi-tenancy	5.3.0
FlashArray with secure multi-tenancy	6.6.11
FlashArray File Services support	6.0.2
Quota policy support for FlashArray File Services	6.1.7
FlashArray with VLAN binding	6.4.1

FlashBlade

FlashBlade must run Purity version 2.2.0 or later.

Cluster node requirements

note

PX-CSI supports Secure Boot-enabled environments and does not require additional configuration.

FlashArray

Category	Requirement
Packages	Ensure that the latest versions of the following packages are installed on nodes where you plan to run PX-CSI: RHEL iscsi-initiator-utils device-mapper-multipath kpartx (installed as part of device-mapper-multipath) Ubuntu open-iscsi multipath-tools kpartx (installed as part of multipath-tools) Debian open-iscsi multipath-tools kpartx (installed as part of multipath-tools) SUSE Linux Enterprise Server open-iscsi multipath-tools kpartx (installed as part of multipath-tools) Note: For NVMe-oF/TCP protocol, you need multipath version 0.8.7 or later.
Red Hat systems	Ensure that the second action, CAPACITY_DATA_HAS_CHANGED, is uncommented in the 90-scsi-ua.rules file, and restart the udev service.
CSI snapshot feature	Install the Snapshot controller and deploy the CRDs available here in your Kubernetes cluster.
FC protocol (optional)	If you are using the FC protocol, ensure that the latest FC initiator software is installed.
NVMe CLI (optional)	If you are using the NVMe protocol, ensure that the following NVMe CLI version is installed: RHEL earlier than 9.4/Ubuntu earlier than 22.04: NVMe CLI version 1.16 RHEL 9.4 to 9.5/Ubuntu 22.04 or later: NVMe CLI version 2.6 RHEL 9.6 or later: NVMe CLI version 2.11

FlashBlade

NFS utilities — Ensure that the latest version of NFS utilities is installed on all nodes, including the master node.

Network requirements

PX-CSI supports IPv4, IPv6, and dual-stack configuration for networking.

FlashArray

• Synchronize all cluster nodes using the Network Time Protocol (NTP). Time skew between nodes can cause unexpected behavior or service disruptions.
• Ensure the FlashArray management IP address is accessible by all nodes.
• Verify that your cluster has an operational FlashArray with an existing data plane connectivity layout.
• Use one of the following storage networking protocols supported by Portworx CSI:
  • iSCSI: For block storage over IP networks.
  • NVMe-oF RoCE or NVMe-oF TCP: For high-performance and low-latency storage access.
  • Fibre Channel (FC): For dedicated storage area networks.
• If using iSCSI:
  • Ensure that the storage node iSCSI initiators are on the same VLAN as the FlashArray iSCSI target ports.
  • If using multiple network interface cards (NICs) to connect to an iSCSI host, ensure all NICs are accessible from the FlashArray management IP address.
• If using Fibre Channel:
  • Ensure that the storage node Fibre Channel WWNs are correctly zoned to the FlashArray Fibre Channel WWN ports.
• Add the following PX-CSI telemetry endpoints on port 443 to networking allow list:
  • https://rest.cloud-support.purestorage.com
  • https://register.cloud-support.purestorage.com

FlashBlade

• Synchronize all cluster nodes using the Network Time Protocol (NTP). Time skew between nodes can cause unexpected behavior or service disruptions.
• Ensure FlashBlade is accessible as a shared resource from all cluster nodes.
• Verify that both the NFSEndPoint and MgmtEndPoint IP addresses are reachable from all nodes.
• Add the following PX-CSI telemetry endpoints on port 443 to networking allow list:
  • https://rest.cloud-support.purestorage.com
  • https://register.cloud-support.purestorage.com

Portworx Operator version

The Portworx Operator manages the lifecycle of PX-CSI. Use the following Operator versions for compatibility with your PX-CSI release:

PX-CSI version	Portworx Operator version
25.6.0 or earlier	24.1.2 or later
25.8.0 or later	25.4.0 or later

Supported platform versions

Portworx CSI supports the following Kubernetes platforms and versions:

Platform	Supported versions
On-premises Kubernetes	1.30, 1.31, 1.32, 1.33
Red Hat OpenShift Container Platform (OCP)	4.15, 4.16, 4.17, 4.18, 4.19
Google Anthos	1.30.0-gke.1930, v1.31.3-gke.100, 1.32.300-gke.85
Rancher (RKE2)	v1.28.14+rke2r1, v1.28.15+rke2r1, v1.29.15+rke2r1, v1.30.11+rke2r1, v1.31.7+rke2r1, v1.32.5+rke2r1, v1.33.4+rke2r1
Azure Kubernetes Service (AKS)	1.30, 1.31, 1.32, 1.33