Portworx Operator 25.6.0 is now GA!

Portworx Releases
1

Hello Everyone,

We’re excited to announce that the latest version of Portworx Operator 25.6.0 is now generally available (GA). This release includes new capabilities and fixes driven by key customer requests and is compatible with Pure Storage FlashArray and FlashBlade.

Key Highlights
Two‑Node Arbiter (TNA) support for OpenShift

  • Portworx operator now supports deployment of Red Hat OpenShift two‑node with arbiter (TNA) clusters for edge deployments, so you get HA without needing a full three‑node storage footprint. Note: Requires Portworx Enterprise 3.5.2 or later and OpenShift Container Platform 4.20.11 or later.

Priority class configuration for all Portworx components

  • You can now configure priority classes for Portworx components using the ComponentK8sConfig custom resource. This lets platform teams ensure critical Portworx pods are scheduled with higher priority and are less likely to be evicted under cluster resource pressure, improving storage and control‑plane availability during failures or upgrades.

OpenShift dynamic plugin configuration enhancements

  • Configure custom images for px‑plugin, px‑plugin‑proxy, and only deploy them when the console plugin is enabled. In addition you can configure resource limits, tolerations, and placement for these components via ComponentK8sConfig, giving you tighter control over image sources and operation.

Autopilot Prometheus metrics and alerts

  • The Operator now exposes Prometheus metrics for Autopilot and introduces the AutopilotActionFailed alert when an action for a rule object fails. This gives you Real‑time visibility into Autopilot rule evaluation.

Automated pxfslibs update (air‑gapped clusters)

  • The Operator can now deploy and manage the pxfslibs DaemonSet, automating Portworx filesystem dependency updates in air‑gapped environments, with on demand trigger.

Usage Instructions

Additional Resources and Documentation