Portworx Enterprise 2.10.0 is now GA

We are very pleased to announce that 2.10.0 is now GA . This release includes several new features and improvements as well as key bug fixes. Here is the list of key features and improvements:

New features

Portworx by Pure Storage is proud to introduce the following new features:

  • The Portworx Application Control feature provides a method for controlling an individual Portworx volume’s IO or bandwidth usage of backend pool resources. Portworx volumes are created from a common backend pool and share their available IOPS and bandwidth amongst all other provisioned Portworx volumes.
  • The volume trash can feature provides protection against accidental or inadvertent volume deletions which could result in loss of data. In a clustered environment such as Kubernetes, unintended deletion of a PV or a namespace will cause volumes to be lost. This feature is recommended in any environment which is prone to such inadvertent deletions, as it can help to prevent data loss.
  • You can enable automatic filesystem trimming (auto fstrim) at the volume, node, or cluster level. When you enable auto fstrim at the cluster or node level and enable nodiscard on your volumes, auto fstrim monitors the unused space in all filesystems mounted on Portworx volumes and automatically triggers a trim job to return unused space back to the pool, and you do not have to manually issue trim jobs.


Improvement Number Improvement Description
PWX-20674 In Async DR setup, before creating a cluster pair, the DR license is checked on both the clusters. The cluster pair request will error out if only one of the clusters has DR license set.
PWX-21318 Users can set the frequency of full backups using pxctl cluster options update -b <number> . The default value is 7, and you can check the value that is set with pxctl cluster options list . The number controls the number of incremental backups made before a full backup is done.
PWX-21024 This fix adds --secret_key and --secret_options that allows users to propagate Kubernetes secret config information to the cli and the backend during volume import.
PWX-19780 Local volumes that are pending due to ha-increase will now appear when using pxctl volume list --node <node> .
PWX-20210 Added support for specifying throughput parameter for gp3 drive types in AWS. The throughput parameter can only be specified at install time. Portworx currently does not allow a way to change the throughput parameter once installed. One can still change the throughput of any drives directly from the AWS console.
PWX-22977 Sometimes cloudsnaps can fail with InternalServerError , resulting in cloudsnap backup failures and the need for user intervention to reissue the cloudsnap command for the same volume. This fix increased the aws-sdk retries and also added back-off retries.
PWX-21122 VPS users now have control at the pool level with the new built-in topologyKey portworx.io/pool to allow volume affinity and anti-affinity to work for individual pools. Users can now control volume placement topology at the narrower level of pool. This allows finer control than the default topology of nodes.
PWX-20938 Added a VolumePlacementStrategy template for use with StatefulSets that allows volume affinity and anti-affinity with volumes belonging to the same StatefulSet pod. Use the key/value px/statefulset-pod"/"${pvc.statefulset-pod} in a matchExpression . With this, you can ensure volumes in the same StatefulSet pod do or do not land on the same node.

Here is a full draft of release notes. Also note that Portworx 2.10 is the last release where Ubuntu 16.04 will be supported.