# Portworx Operator 25.5.0 is now GA!

**URL:** <https://forums.portworx.com/t/portworx-operator-25-5-0-is-now-ga/2276>\
**Category:** Portworx Releases\
**Tags:** release, operator\
**Created:** [November 20, 2025, 12:24pm UTC](https://forums.portworx.com/t/portworx-operator-25-5-0-is-now-ga/2276 "2025-11-20T12:24:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![AnmolSachan](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/anmolsachan/32/830_2.png) [@AnmolSachan](https://forums.portworx.com/u/AnmolSachan)\
**Post date:** [November 20, 2025, 12:24pm UTC](https://forums.portworx.com/t/portworx-operator-25-5-0-is-now-ga/2276/1 "2025-11-20T12:24:07Z")

</div>

Hello Everyone,

We’re excited to announce that the latest version of **Portworx Operator 25.5.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**

- Support for external user‑managed **Prometheus** for monitoring and **Autopilot**. This provides a clear way to use a user‑managed Prometheus instead of the Portworx‑managed Prometheus, eliminating conflicts that can occur when two Prometheus deployments are present.

- A new **DeleteStrategy** for the **StorageCluster** called **UninstallAndDelete** on **vSphere** , **AWS** , **GKE** , and **Azure**. This strategy removes all Portworx components, wipes storage devices, deletes Portworx metadata from KVDB, and **removes the associated cloud drives.**

- A new **ignoreVolumes** spec for the **StorageCluster** delete strategy. By default set to false, it prevents a StorageCluster uninstall if **PVCs** are present in the cluster for UninstallAndWipe or UninstallAndDelete delete strategy, which helps avoid unintended data loss. This introduces a change in behaviour for uninstall operation and ignoreVolumes need to be set to true if you intend to uninstall while PVCs are still present.

- On OpenShift clusters, the Operator now creates StorageClasses by default(RWX Block) when the HyperConverged custom resource for OpenShift Virtualization is detected. This ensures seamless integration with OpenShift Virtualization, eliminates manual setup steps, and enables users to immediately provision persistent storage for virtual machines.

**Usage Instructions**

- [Portworx Operator upgrade documentation](https://docs.portworx.com/portworx-enterprise/platform/upgrade/upgrade-operator)

- [Monitor Clusters on Kubernetes](https://docs.portworx.com/portworx-enterprise/operations/monitoring/monitor-portworx-cluster)

**Additional Resources and Documentation**

- [Release Notes](https://docs.portworx.com/release-notes/portworx-operator)

- [Helm chart reference](https://docs.portworx.com/portworx-enterprise/reference/helm-chart)