A stateful application needs storage that remains usable as its pods and worker machines change. Portworx provides a storage platform for Kubernetes applications, managing volumes and the underlying storage design across the selected environment. Teams evaluate it when they need coordinated storage operations alongside their workloads. Durability and availability depend on the chosen topology, replication, disks and failure domains; adopting the platform still requires a plan for application-consistent backups, upgrades and recovery.
Current guidance
Current Portworx Enterprise documentation distinguishes converged and disaggregated deployments, storage backends, KVDB choices and platform-specific installation paths, including Helm. Use that supported platform guidance rather than treating the recovered chart as a portable default for any cluster.
Choose Portworx against the actual stateful workload and operating model: failure domains, replication, available disks, node/kernel support, encryption, recovery targets and license terms all matter. StorageClass names alone do not describe the underlying durability or capacity policy. Reserve resources and check how upgrades interact with node maintenance and volume attachment before introducing application data.
For a packaging change, inventory StorageClusters, storage classes, volume identities, encryption keys and external dependencies. Follow the documented operator and data-plane upgrade ordering for the selected environment. Rehearse application-consistent backup and restore on separate storage, and define recovery from a failed node or unavailable control plane. Do not uninstall the old release or delete its storage custom resources merely to clear a Helm ownership conflict; that can affect the data system itself.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub does not mark portworx/helm archived or disabled; this does not establish active maintenance, support or compatibility. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Original publication: 2018-09-22T08:58:57+00:00. Preserved for context. Commands, versions, prices and results below reflect the original research.
Portworx is a software defined persistent storage solution designed and purpose built for applications deployed as containers, via container orchestrators such as Kubernetes, Marathon and Swarm. It is a clustered block storage solution and provides a Cloud-Native layer from which containerized stateful applications programmatically consume block, file and object storage services directly through the scheduler.
The post Portworx appeared first on kubedex.com.
Sources & further reading
Spotted something that needs another look?
Help improve this page →