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 minimum of three nodes cluster. All node must meet the following specifications:

Hardware requirements

Category	Requirement
CPU	1 CPU
RAM	2 GB minimum
Disk Space	/var: 20 GB free /opt: 3 GB free
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 System support	6.0.2
Quota policy support for FlashArray File Systems	6.1.7
FlashArray with VLAN binding	6.4.1

FlashBlade

FlashBlade is running Purity version 2.2.0 or later.

Software 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 mulipath-tools) Debian open-iscsi multipath-tools kpartx (installed as part of mulipath-tools) SUSE Linux Enterprise Server open-iscsi multipath-tools kpartx (installed as part of mulipath-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 version earlier than 9.4/Ubuntu version earlier than 22.04: NVMe CLI version 1.16 RHEL version 9.4 or later/Ubuntu version 22.04 or later: NVMe CLI version 2.6 or later

FlashBlade

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

Network requirements

Ensure that all cluster nodes are synchronized with Network Time Protocol (NTP). Time skew between nodes might cause unexpected behavior or service disruptions.

Network Configuration requirements

FlashArray

• Ensure the FlashArray management IP address is accessible by all nodes.
• Verify that your cluster has an operational FlashArray with an existing dataplane 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 robust, 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 is correctly zoned to the FlashArray Fibre Channel WWN ports.

FlashBlade

• 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.

Port configuration requirements

Ensure that your network settings are configured correctly to facilitate seamless communication and effective telemetry monitoring.

• Communication: Required for pod-to-pod interaction and external connections.
• Telemetry: Ensures proper monitoring and analytics.

East-to-west

Kubernetes	OpenShift	Description
9001	17001	Portworx management port [REST]
9002	17002	Portworx node-to-node port [gossip]/UDP
9003	17003	Portworx storage data port
9004	17004	Portworx namespace [RPC]
9012	17009	Portworx node-to-node communication port [gRPC]
9013	17010	Portworx namespace driver [gRPC]
9014	17011	Portworx diags server port [gRPC]
9018	17015	Portworx kvdb peer-to-peer port [gRPC]
9019	17016	Portworx kvdb client service [gRPC]
9021	17018	Portworx gRPC SDK gateway [REST]
9022	17019	Portworx health monitor [REST]
9029	17021	Telemetry log uploader
12002	20002	Telemetry phone home

Inbound

Kubernetes	OpenShift	Description
9001	17001	Portworx management port [REST]
9021	17018	Portworx gRPC SDK gateway [REST]

Outbound

Kubernetes	OpenShift	Description
443	443	Telemetry: logs-01.loggly.com rest.cloud-support.purestorage.com register.cloud-support.purestorage.com

Supported Platform Versions

Portworx CSI supports the following Kubernetes platforms and versions:

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