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 FlashArray and FlashBlade 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, see Upgrade Portworx CSI for upgrade instructions.

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

PX-CSI 26.3.0

September 29, 2026

Supported Operator version: 26.4.0 or later

What's New

• FlashBlade snapshot restore to a new volume
  

  PX-CSI now supports restoring a FlashBlade Direct Access (FBDA) snapshot to a new volume instead of overwriting the source file system in place. Create a PVC with a dataSource referencing a VolumeSnapshot of a FlashBlade file system to provision a new volume from the snapshot's data. For more information, see Snapshot of FlashBlade PVC.

• Volume eradication on deletion
  

  PX-CSI now supports immediately eradicating FlashArray and FlashBlade volumes when they are deleted from Kubernetes, instead of leaving them in the pending eradication queue. Set eradicate_on_delete: "true" in the StorageClass parameters to control eradication per StorageClass. For more information, see Delete a PVC.

• FlashArray File Services PVC size enforcement

  PX-CSI now enforces the capacity requested by each persistent volume claim (PVC) provisioned on FlashArray File Services. When PX-CSI creates a volume, the driver automatically creates or reuses a size-derived managed quota policy on the FlashArray and attaches it to the managed directory for the volume, so the mounted volume reflects and enforces the requested PVC size. For more information, see Dynamic Provisioning of FlashArray File Services.

• ARM (arm64) architecture support
  

  PX-CSI now supports ARM-based (arm64) Kubernetes nodes. For more information, see System Requirements.

• Multi-SAN protocol support
  

  PX-CSI now supports assigning different SAN protocols to different nodes within a single Kubernetes cluster. Each node uses one protocol—iSCSI, NVMe-TCP, NVMe-RoCE, NVMe-oF FC, or Fibre Channel—configured through PURE_FLASHARRAY_SAN_TYPE in StorageCluster.spec.nodes[].env. For more information, see Configure multi-SAN protocol support.

• Cross-array FlashArray snapshot
  

  PX-CSI now supports creating cross-array snapshots that transfer a FlashArray block volume snapshot asynchronously to a different FlashArray in the same cluster. Specify the target array using the portworx.io/target-array-id annotation on a VolumeSnapshot or as a VolumeSnapshotClass parameter. Requires Purity 6.6.1 or later on both source and destination arrays. For more information, see Snapshot of FlashArray PVC.

• ActiveCluster support for FlashArray Realms
  

  PX-CSI now supports FlashArray ActiveCluster stretched pods that connect two realms (secure multi-tenancy), one on each array, for iSCSI and Fibre Channel (FC) protocols. For more information, see Use FlashArray ActiveCluster.

• FlashArray File Services multi-server support
  

  PX-CSI now supports provisioning FlashArray file service volumes on a specific NFS server using the pure_nfs_server StorageClass parameter. This enables data access isolation on a per-StorageClass basis, consistent with FlashBlade multi-server support added in 26.2.0. Requires Purity 6.8.7 or later. For more information, see StorageClass reference.

• TLS certificate verification for management API connections
  

  PX-CSI now supports TLS certificate verification for FlashArray and FlashBlade management API connections. Set VerifySSL: true in the SSLOptions object in pure.json to enable certificate validation. Optionally, provide a CABundle (base64-encoded PEM) when the endpoint uses a certificate signed by a private CA. For more information, see pure.json reference.

• Per-array provisioning control
  

  You can now exclude individual FlashArray or FlashBlade backends from new volume provisioning by setting ProvisioningDisabled: true in the Configuration object for that backend entry in pure.json. Existing volumes remain unaffected. All other operations, including attaching, detaching, and creating snapshots, also remain unaffected. For more information, see pure.json reference.

• volumeWWN in FlashArray volume context
  

  PX-CSI now adds the volumeWWN attribute to the volume context (volumeAttributes) of FlashArray Direct Access (FADA) persistent volumes.

Resolved Issues

Issue Number	Issue Description	Severity
PWX-56676	When multiple management endpoints are configured for a FlashArray, PX-CSI did not attempt the remaining endpoints when one endpoint triggered a circuit breaker, causing provisioning operations to fail.	Major
PWX-54219	Restoring a FlashBlade Realm snapshot using realm-scoped user credentials failed. Fixed in Purity version 4.7.10 and later.	Major
PWX-60116	Resizing a FlashArray File Services PVC failed with error ControllerExpandVolume failed: failed to update volume	Minor