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 |
|
| Network Connectivity | Bandwidth:
|
| Node Type | Bare metal or virtual machine (VM) |
Cluster node requirements
note
PX-CSI supports Secure Boot-enabled environments and does not require additional configuration.
- FlashArray block volumes
- FlashArray File Services / FlashBlade
| Category | Requirement |
|---|---|
| Packages | Ensure that the latest versions of the following packages are installed on nodes where you plan to run PX-CSI:
|
| 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:
|
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
- FlashBlade
- 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 that all NICs can access the FlashArray data IP address. For multi-subnet environments with network policies that restrict cross-subnet communication, consider using subnet-aware iSCSI login. For more information, see Configure subnet-aware iSCSI login.
- 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
443to networking allow list:https://rest.cloud-support.purestorage.comhttps://register.cloud-support.purestorage.com
- 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
NFSEndPointandMgmtEndPointIP addresses are reachable from all nodes. - Add the following PX-CSI telemetry endpoints on port
443to networking allow list:https://rest.cloud-support.purestorage.comhttps://register.cloud-support.purestorage.com
Compatibility and interoperability matrix
For information about supported Kubernetes platforms and distributions, compatible PX-CSI and Portworx Operator versions, minimum Purity version requirements, and supported features per backend, see the Compatibility and Interoperability Matrix.