Pure Storage has released Portworx Enterprise 2.8. With new capabilities such as dynamic storage provisioning on FlashArray and FlashBlade, and unified visibility and support via Pure1, Portworx enables containerised workloads to run seamlessly across the cloud, bare metal infrastructure, Pure Storage arrays, and even competitive storage solutions, said the firm.
“Pure and Portworx together are redefining what storage for modern, cloud-native applications looks like. By delivering storage that can be orchestrated entirely through Kubernetes, Pure is delivering a seamless hybrid cloud experience and changing outcomes for customers,” said Murli Thirumale, VP and GM, Cloud Native Business Unit, Pure Storage.
With the latest release of Portworx Enterprise 2.8, customers get the same cloud-like experience for Kubernetes apps wherever they live, with broad Kubernetes ecosystem support. New capabilities include:
Portworx delivers the simplest way to run Kubernetes applications at enterprise levels of scale and resiliency: The 2.8 release of Portworx Enterprise goes significantly beyond the capabilities offered by other storage solutions who are limited to the “connector” approach facilitated by the Kubernetes Container Storage Interface (CSI), resulting in least common denominator features and limited scale. With a Kubernetes-native software approach built to support enterprise levels of scale and resiliency, the solution combines cloud-native storage management and data protection services with best-of-breed Pure Storage FlashArray and FlashBlade for seamless deployment. Now when users provision container-native volumes through Portworx, storage volumes or file systems are automatically created on FlashArray and FlashBlade. This allows true storage-as-code, as volumes and file systems can be provisioned using Kubernetes without the need to directly interface with the backing storage arrays. Container-native volumes receive the full suite of Portworx container storage management features, including backup, disaster recovery, security, auto-scaling, and migration – features that aren’t tied to hardware and travel with the containerized application as it moves between on-prem and cloud deployments. With this new integration, customers can manage their modern applications in a Kubernetes-native way, while taking advantage of the enterprise capabilities of their Pure arrays such as deduplication and compression, achieving data reduction levels up to 10:1 depending on workload and a demonstrated 99.9999% reliability across 40,000+ arrays.
Predictive capabilities of Pure1, now for Kubernetes apps running on Portworx: With the latest Portworx release, Kubernetes cluster and volume usage metrics collected by Portworx will be sent to Pure1, providing a unified observability stack and support experience for a customer’s Kubernetes applications with Portworx in the Pure1 portal, allowing customer to see their deployments end-to-end and troubleshoot issues with Kubernetes applications. Additionally, as Pure1 collects data necessary to understand deployment patterns, it enables customers to benefit from the predictive support capabilities of Pure1, powered by the Meta AI engine, which aims to detect anomalies and suggest resolution advice before issues become outages.
A better container-native storage experience for VMware Tanzu as well as any CSI-compatible storage system: The latest release extends Portworx support for leading Kubernetes platforms with addition of VMware Tanzu (TKG) support via the native Tanzu CSI driver. This means that customers can benefit from container-granular data management such as backup & recovery, encryption, and migration regardless of the storage backing their VMware environment including with vSAN, VVols, and VMFS datastores, or cloud block storage providers. Additionally, with Portworx Enterprise 2.8 supporting the latest CSI specification, Portworx can provide a consistent, Kubernetes-native experience for applications running on any enterprise storage that supports CSI.
Portworx Enterprise 2.8 is available from June 2021.
Discussion about this post