Portworx Operator 25.3.0 is now GA!

Hello Everyone,

We are excited to announce that the latest version of Portworx Operator 25.3.0 is now Generally Available. The new version consists of solutions and fixes for key customer requests, which can be used with Pure Storage FlashArray and FlashBlade.

Caveat for OpenShift users
If you are running an OpenShift versions 4.15 and earlier, do not upgrade to Operator version 25.3.0. This version causes excessive Secret object creation due to repeated ServiceAccount updates, which significantly increases API server load. For more information about the workaround, see release notes.

Key Highlights

  • A new ComponentK8sConfig Custom Resource, allowing configuration of resource requests, limits, labels, annotations, tolerations, and placement rules for all Portworx components. This eliminates fragmented configurations across the StorageCluster CRD, with support for migration to the new Custom Resource.

Other Notable Improvements

  • Starting with Kubernetes version 1.31, in-tree storage drivers have been deprecated, and the CSI drivers must be used. In conformance with this Portworx Operator will now automatically set the CSI configuration to enabled if the CSI spec is left empty or explicitly disabled. If CSI is already enabled, no changes will be made.

  • Portworx Operator will create a default VolumeSnapshotClass named px-csi-snapclass, enabling customers to use volume snapshots and VM snapshots out of the box for KubeVirt.

  • Portworx Operator StorageCluster CR will report a new state called UpdatePaused when an upgrade is paused. StorageCluster events and logs will provide additional context about the paused upgrade. This shall help troubleshoot upgrade issues due to issues such as vm live migration failures.

Usage Instructions

Additional Resources and Documentation