Portworx CSI Release Notes

Portworx CSI (PX-CSI) is a lightweight storage orchestration solution that uses the Kubernetes Container Storage Interface (CSI) framework to integrate the Everpure platforms.

PX-CSI integrates with Kubernetes to directly access FlashArray Direct Access volumes (FADA) and FlashBlade Direct Access volumes (FBDA).

If you're setting up PX-CSI for the first time, see Install Portworx CSI. If you're already using PX-CSI, upgrade to the latest version. For upgrade instructions, see Upgrade Portworx CSI.

For information about supported versions, release numbering, and support phases, refer to the PX-CSI Life Cycle Support Policy.

PX-CSI 26.2.1

June 29, 2026

Supported Operator version: 26.3.0 or later

What's New

• NVMe over Fibre Channel (NVMe-oF FC) support
  

  PX-CSI now supports NVMe over Fibre Channel (NVMe-oF FC) as a storage transport protocol for FlashArray. At node startup, the driver reads the host NQN and FC WWPNs from the system and registers them in the StorageNodeInitiator resource. Target discovery is handled automatically by the FC fabric through zoning, requiring no manual nvme-connect configuration. For more information, see System Requirements.

• Dynamic credential rotation for px-pure-secret
  

  PX-CSI now watches the px-pure-secret Kubernetes Secret for changes and automatically reloads backend credentials without a pod restart. When credentials expire or become invalid, CSI volume operations return an authentication error so workloads detect the failure immediately. For more information, see Use FlashArray as backend storage.

• Dynamic QoS and tag modification using VolumeAttributesClass
  

  PX-CSI now supports the Kubernetes VolumeAttributesClass resource, enabling you to modify QoS limits and backend tags on existing FlashArray block volumes without reprovisioning. Set max_iops, max_bandwidth, pure_backend_tags, or pure_backend_remove_tags as mutable parameters in a VolumeAttributesClass and reference it from a PVC to apply the changes at runtime. For more information, see Modify volume attributes of a PVC.

• Custom tags for FlashArray block volumes
  

  PX-CSI now supports custom metadata tags on FlashArray block volumes. Use the pure_backend_tags StorageClass parameter to apply semicolon-separated key:value tags at provisioning time, enabling you to identify and filter CSI-managed volumes on the FlashArray by environment, team, or cost allocation. For more information, see Add custom tags to FlashArray block volumes.

• Volume resource-only backup and restore with Portworx Backup
  

  PX-CSI now supports volume resource-only (VRO) backup and restore with Portworx Backup. A VRO backup captures Kubernetes resource definitions—including PVC and PV specifications and application manifests—without taking storage snapshots. When you restore a VRO backup to a new or rebuilt cluster, PX-CSI reconnects to the existing backend volumes on the FlashArray or FlashBlade without any data migration. For more information, see Back up and restore PX-CSI clusters using Portworx Backup.

Resolved Issues

Issue Number	Issue Description	Severity
PWX-55937	When the StorageCluster resource is not found, the node plugin continues to start and operates with default configuration instead of failing.	Minor
PWX-56138	When a Fibre Channel (FC) port comes online after PX-CSI starts on a host with multiple FC HBA ports, the WWPN comparison against the Purity host fails and blocks all new volume attachments.	Minor
PWX-56482	When an input/output error occurs while checking a device for an existing file system, PX-CSI fails to detect the existing file system.	Major
PWX-56608	When you specify a DNS name as the FlashBlade NFS endpoint in pure_nfs_endpoint or the px-pure-secret, PVC provisioning fails.	Minor

PX-CSI 26.2.0

June 9, 2026

Supported Operator version: 26.2.0 or later

What's New

• FlashBlade with secure multi-tenancy
  

  PX-CSI now supports FlashBlade Realms for secure multi-tenancy with isolated credentials and resource boundaries. Configure the realm field in pure.json and use the pure_nfs_policy and pure_nfs_server StorageClass parameters to create file systems in the realm. Secure multi-tenancy requires Purity version 4.6.1 or later. For more information, see Use FlashBlade as Backend Storage and Dynamic Provisioning of FlashBlade File Systems.

• FlashBlade multi-server support
  

  PX-CSI now supports provisioning file systems on specific NFS servers instead of the default _array_server to enable data access isolation. Use the pure_nfs_policy, pure_nfs_server, and pure_nfs_endpoint StorageClass parameters. Requires Purity version 4.6.1 or later. For more information, see StorageClass reference.

• Native NVMe multipath support
  

  PX-CSI now supports Native NVMe Multipath for NVMe with FlashArray. The driver automatically detects whether the host uses Native NVMe Multipath or DM-multipath and discovers the correct device path. This feature provides faster failover, improved performance, and simplified operations on modern Linux distributions that default to kernel-managed NVMe multipathing. No configuration changes are required. For more information, see System Requirements.

• Volume Group Snapshot Support for FlashArray block volumes
  

  PX-CSI now supports the VolumeGroupSnapshot resource, enabling crash-consistent snapshots of multiple FlashArray-backed PVCs in a single operation. PX-CSI maps each group snapshot to a FlashArray protection group snapshot, ensuring that all member volumes are snapshotted at the same point in time. Kubernetes creates individual VolumeSnapshot objects for each PVC, which you can use with the standard restore workflow. Requires Purity version 6.4.10 or later. For more information, see Snapshot of FlashArray PVC.

• Block PV deletion when snapshots exist
  

  PX-CSI now supports blocking PersistentVolume deletion when the backend volume has existing snapshots. Set the ENABLE_VOLUME_DELETION_WITH_SNAPSHOTS environment variable to false in the StorageCluster specification to enforce this check. When enabled, PX-CSI returns a FailedPrecondition error and generates a VolumeFailedDelete Kubernetes event when snapshots are detected, preventing accidental data loss. For more information, see Delete a PVC.

• Increased volume attachments per node
  PX-CSI now supports attaching up to 1024 volumes to a single node, enabling higher workload density without any architectural constraints. For more information, see Volume attachment limits.

• Host connection health monitoring
  

  PX-CSI now exposes Prometheus metrics for the health of host storage connections. The CSI node driver periodically checks iSCSI sessions, NVMe subsystems, NVMe connections, and FC hosts and remote ports, and reports their status as Prometheus metrics labeled with the node name. Use these metrics to detect degraded or lost storage connections before they affect your workloads. For more information, see Host connection health metrics.

• NFS over TLS for FlashArray file services
  

  PX-CSI now supports NFS over TLS for FlashArray file services. Add xprtsec=tls to mountOptions in the StorageClass to enable TLS for NFS traffic. This feature supports NFSv3 and NFSv4.1 and requires Purity version 6.10.6 or later, and worker nodes must have nfs-utils, ktls-util (tlshd), and openssl installed. For more information, see Dynamic Provisioning of FlashArray File Services.

• NFS over TLS for FlashBlade file systems
  

  PX-CSI now supports NFS over TLS for FlashBlade file systems. Add xprtsec=tls to mountOptions in the StorageClass and specify pure_nfs_policy that references an export rule with TLS enabled. This feature supports NFSv3 and NFSv4.1 and requires Purity version 4.6.0 or later, and worker nodes must have nfs-utils, ktls-util (tlshd), and openssl installed. For more information, see Dynamic Provisioning of FlashBlade File Systems.

• Two-Node Arbiter (TNA) support for OpenShift
  

  PX-CSI now supports Red Hat OpenShift two-node with arbiter (TNA) clusters for edge deployments.

• Single node cluster support
  

  PX-CSI now supports running on a single-node Kubernetes cluster. This feature allows you to deploy PX-CSI in environments with limited resources. For more information about PX-CSI requirements, see System Requirements.

• Wind River Cloud Platform support
  

  PX-CSI now supports Wind River Cloud Platform (WRCP) clusters running version 25.09. For more information about WRCP, see Wind River Cloud Platform.

Resolved Issues

Issue Number	Issue Description	Severity
PWX-53602	In ActiveCluster setups, when PURE_ISCSI_ALLOWED_IFACES is configured and participating FlashArrays present different LUNs for a PVC, workloads that consume that PVC might fail to reach the Running state because PX-CSI was unable to mount the PersistentVolumes.	Major
PWX-54578	In ActiveCluster setups, when PURE_ISCSI_ALLOWED_IFACES is configured and the LUN ID associated with a PVC is greater than 255, NodeStageVolume might fail and workloads that use the associated PVC fail to reach the Running state.	Major

Known Issues

• PWX-54219: Restoring from a snapshot for file systems in a FlashBlade Realm is not supported when you use realm-scoped user credentials.

  Workaround: Use FlashBlade array-scoped (global) credentials instead of realm-scoped credentials for the restore operation.

  Affected version: 26.2.0