Skip to main content
Version: 3.6

Configure Portworx Components

This section outlines how to configure essential Portworx Components that provide storage orchestration, dynamic volume management and help with monitoring storage nodes in Kubernetes environments.

Portworx Operator is a primary component that manages the complete Portworx Enterprise deployment in Kubernetes. The operator deploys and manages the complete life cycle of the Portworx pods. Portworx Operator has its own release cycle, and the updates provided are in the Operator Release Notes.

When you install Portworx Enterprise, Portworx Operator deploys the following components in the Portworx stack by default, unless you’ve customized the installation to disable them.

  1. Portworx Autopilot - A rule-based engine that responds to changes based on metric conditions and then automatically takes actions such as adding capacity, rebalancing storage and so on. Autopilot allows you to specify monitoring conditions along with actions it should take when those conditions occur. For information on Autopilot and how to enable or upgrade Autopilot, see Portworx Autopilot. To know about how Autopilot can be used to scale your clusters, see Expand your Storage Pool with Autopilot. Autopilot has its own release cycle, and the updates are captured in the Autopilot Release Notes.

  2. Portworx Stork - Portworx's storage scheduler for Kubernetes that helps achieve tighter integration of Portworx with Kubernetes. Stork allows users to co-locate pods with their data, provides seamless migration of pods in case of storage errors, and makes it easier to create and restore snapshots of Portworx volumes. Stork consists of 2 components, the Stork scheduler and an extender. Both of these components run in HA mode with 3 replicas by default. For information on Stork and how to enable or upgrade Stork, see Portworx Stork. Stork has its own release cycle, and the updates are captured in the Stork Release Notes.

  3. Portworx Telemetry - An integration that automatically uploads the diagnostics bundle and real-time Prometheus metrics from your Portworx cluster to Pure1. This enables support teams to proactively monitor and troubleshoot your clusters. For information on how to enable or disable telemetry, see Portworx Telemetry. When telemetry is enabled, you can also use Pure1 AI Copilot to interact with your Portworx storage clusters using natural language. For more information, see Portworx on Pure1 AI Copilot.

  4. CSI Driver - A standardized plugin that manages the full Kubernetes volume lifecycle including dynamic provisioning, cloning, expansion, snapshotting (local and cloud), volume restoration, shared (RWX) volumes, raw block volumes, ephemeral storage, and encryption/RBAC-based security via native Kubernetes APIs. For more information, see Manage Volume Lifecycle with CSI Driver

When you upgrade Portworx Enterprise, these components are automatically upgraded. The updated plugin version is aligned with the Portworx Enterprise version you are upgrading to.

For Portworx Enterprise on Openshift clusters, the following integration is available:

Portworx OpenShift Dynamic Plugin - An integrated storage observability and management component that is directly in the OpenShift console. It simplifies observability by monitoring and troubleshooting for Portworx storage clusters, Kubernetes applications and OpenShift integrations such as KubeVirt. For information on Portworx OpenShift Dynamic Plugin, and how to enable or upgrade the plugin, see Enable or Upgrade Portworx OpenShift Dynamic Plugin. Portworx OpenShift Dynamic Plugin (OCP) has its own release cycle and the updates are in the Portworx OCP Release Notes.

For Portworx Enterprise with Everpure FlashArray and Flashblade, the following integrations are available as early access:

  1. PX-CSI Integration - An improved implementation of Direct Access Volumes where PX-CSI can be integrated with Portworx Enterprise. For more information, see Integrate PX-CSI into Portworx Enterprise.

  2. Portworx Fusion Controller - A unified, application-aware platform that combines Fusion’s fleet-level management with Portworx’s Kubernetes-native data services. Portworx Fusion Controller connects Kubernetes clusters to Fusion fleets, enabling access to storage presets and workloads. For more information, see Enable Portworx Fusion Controller.

Last updated on