Skip to main content
Version: 3.3

System Requirements

Before installing Portworx Enterprise, ensure your environment meets the minimum requirements for a stable and supported deployment. A Portworx cluster must include at least three nodes, each meeting specific hardware, software, and network requirements.

Hardware requirements​

Each node in the Portworx cluster must meet baseline hardware specifications. These vary slightly depending on whether you're using PX-StoreV1 or PX-StoreV2. Requirements include CPU, RAM, disk space and storage drive configuration to ensure optimal operation.

Hardware Requirements
CPUMinimum 4 Cores | Recommended 8 Cores
RAMMinimum 4GB | Recommended 8GB
Disk
  • /var - Recommended 30GB Free
  • /opt - Minimum 3GB Free
    • Backing drive8GB (minimum required)
    128GB (minimum recommended)
    Operating system root partition
  • 64GB is the minimum required size for the root filesystem, which contains the operating system.
    • 128GB minimum recommended
    Storage drivesStorage drives must be unmounted block storage: raw disks, drive partitions, LVM, or cloud block storage.
    Network connectivity

    Bandwidth:

    • 10 Gbps recommended
    • 1 Gbps minimum
    Latency requirements for synchronous replication: less than 10ms between nodes in the cluster.

    Node typeBare metal and virtual machine (VM)

    Software requirements​

    Each node in the Portworx cluster must meet the necessary software requirements, including a supported Linux kernel version, container runtime, and key-value store configuration. Portworx also depends on specific system utilities and settings, such as having swap disabled and NTP enabled, to ensure reliable and consistent cluster behavior.

    SoftwareRequirements
    Linux kernel and distro

    Kernel version 4.18 or greater.
    To check if your Linux distro and kernel are supported, see Supported Kernels.

    DockerVersion 1.13.1 or greater.
    Key-value store

    Portworx needs a key-value store to perform its operations. As such, install a clustered key-value database (kvdb) with a three-node cluster.

    You can also use Internal KVDB during installation. In this mode, Portworx will create and manage an internal key-value store (KVDB) cluster.

    If you plan to use your own KVDB, refer to KVDB for Portworx for details on recommendations for installing and configuring a KVDB cluster.

    Disable swap

    Disable swap on all nodes that will run the Portworx software. Ensure that the swap device is not automatically mounted on server reboot.

    Network Time Protocol (NTP)

    All nodes in the cluster should be in sync with NTP time. Any time drift between nodes can cause unexpected behavior, impacting services.

    Supported hypervisor version​

    Hypervisor
    VMware vSphere
    • Version 7.0
    • Version 8.0

    Network requirements​

    Portworx runs as a pod in a Kubernetes cluster and requires specific ports to be open for node communication, storage operations, and telemetry. These vary slightly between Kubernetes and OpenShift environments.

    East-to-West​

    KubernetesOpenShiftDescription
    900117001Portworx management port [REST]
    900217002Portworx node-to-node port [gossip]/UDP
    Required open when using external KVDB
    900317003Portworx storage data port
    900417004Portworx namespace [RPC]
    901217009Portworx node-to-node communication port [gRPC]
    901317010Portworx namespace driver [gRPC]
    901417011Portworx diags server port [gRPC]
    901817015Portworx kvdb peer-to-peer port [gRPC]
    901917016Portworx kvdb client service [gRPC]
    902117018Portworx gRPC SDK gateway [REST]
    902217019Portworx health monitor [REST]
    902917021Telemetry log uploader
    1200220002Telemetry phone home
    23792379External KVDB (etcd) port
    Open only if you run an external etcd cluster

    Inbound​

    KubernetesOpenShiftDescription
    900117001Portworx management port [REST]
    902117018Portworx gRPC SDK gateway [REST]

    Outbound​

    TypeTCP Port(s)ScopeDestination host(s)Description
    Install / Upgrade443PX install & version updatesinstall.portworx.comRetrieves install spec and helper scripts
    License activation443PAYG licensingrest.zuora.comUsage reporting & license retrieval. Not applicable for air-gapped deployements.
    443PAYG licensingflex1327.compliance.flexnetoperations.comFor licensing to work. Not applicable for air-gapped deployements.
    Telemetry443Cluster registration & metricsregister.cloud-support.purestorage.com,
    rest.cloud-support.purestorage.com    		Registers cluster and uploads usage metrics
    443 / 80Event log uploadslogs-01.loggly.comSends PX log events for support
    9024Portworx version 2.13.7 and olderTelemetry componentsTelemetry data channel
    9029Portworx version 2.13.8 and newerTelemetry componentsTelemetry data channel
    12001Collector serviceTelemetry componentsAggregates data before upload
    12002Heartbeat / phone-homeTelemetry componentsPeriodic health-check pings
    Snapshots / Backups443CloudSnaps, backups, restoresYour S3 or S3-compatible endpointPersist snapshots & object data

    Supported Kubernetes versions​

    Before you install Portworx on any environment, ensure that you're using a supported environment version:

    If your Kubernetes distribution supports multiple Linux distributions and kernel versions, refer to the Supported kernels page to ensure that your kernel version is supported.

    note

    Portworx Enterprise 3.3.0 supports Kubernetes version 1.32, starting from version 1.32.2. Before upgrading Kubernetes to 1.32.2 or later, update the Portworx Stork to version 25.2.2 or above and Portworx Operator to 24.2.3 version or above. For more details, refer to the Portworx Operator 24.2.3 release note

    TypeSupported Versions
    Kubernetes On-prem
    • Kubernetes:
      • 1.27
      • 1.28
      • 1.29
      • 1.30
      • 1.31, starting from 1.31.6
      • 1.32, starting from 1.32.2
    Managed Kubernetes distribution
    • Google Kubernetes Engine (GKE): 1.28.14, 1.29.9, 1.30.12, 1.31.8, 1.32.4
    • Azure Kubernetes Service (AKS): 1.28.14, 1.29.10, 1.30.12, 1.31.8, 1.32.4
    • Amazon Elastic Kubernetes Service (EKS): 1.27.16, 1.28.15, 1.29.13, 1.30.11, 1.31.7, 1.32.3
    • IBM Cloud Kubernetes Service (IKS): 1.29.15, 1.30.13, 1.31.9, 1.32.5

      Note: Operator 23.10.4 or later is required

    • Kubernetes Engine (OKE): 1.28.10, 1.29.1, 1.30.1, 1.32.1, 1.33.0
    • KOPS: 1.28.6, 1.29.2, 1.30.1
    • Rancher Kubernetes Engine 2 (RKE2): 1.28.15, 1.29.13, 1.30.11, 1.31.7

      Note: Portworx supports SUSE Rancher versions 2.9.x and 2.10.x.

    • Mirantis: 1.27.7 (MKE 3.7.3, MCR 23.0.8 ), 1.27.10 (MKE 3.7.6, MCR 23.0.10), 1.27.16 (MKE 3.7.16, MCR 23.0.15)
    • Charmed Kubernetes: Juju version: 3.3
    Distribution Kubernetes
    • Red Hat OpenShift:
      • OpenShift version: 4.14, verified up to 4.14.50, Kubernetes version: 1.27
      • OpenShift version: 4.15, verified up to 4.15.48, Kubernetes version: 1.28
      • OpenShift version: 4.16, verified up to 4.16.39, Kubernetes version: 1.29
      • OpenShift version: 4.17, verified up to 4.17.27, Kubernetes version: 1.30
      • OpenShift version: 4.18, verified up to 4.18.11, Kubernetes version: 1.31

      Note: Supports both bare metal and VM

    • Red Hat OpenShift on IBM Cloud:
      • ROKS version: 4.14, verified up to 4.14.50
      • ROKS version: 4.15, verified up to 4.15.48
      • ROKS version: 4.16, verified up to 4.16.40
      • ROKS version: 4.17, verified up to 4.17.28
      • ROKS version: 4.18, verified up to 4.18.11
    • Red Hat OpenShift Service on AWS:
      • ROSA version: 4.14, verified up to 4.14.46
      • ROSA version: 4.15, verified up to 4.15.48
      • ROSA version: 4.16, verified up to 4.16.40
      • ROSA version: 4.17, verified up to 4.17.29
      • ROSA version: 4.18, verified up to 4.18.14
    • Azure Red Hat OpenShift:
      • ARO version: 4.14, verified up to 4.14.16
      • ARO version: 4.15, verified up to 4.15.49
      • ARO version: 4.16, verified up to 4.16.30
    Tanzu
    • Tanzu Kubernetes Grid Service (TKGS):
      • v1.27.11---vmware.1-fips.1-tkg.2
      • v1.28.8---vmware.1-fips.1-tkg.2 (supported from Portworx version 3.2.1)
      • v1.29.4---vmware.3-fips.1-tkg.1 (supported from Portworx version 3.2.1)
      • v1.30.1---vmware.1-fips-tkg.5 (supported from Portworx version 3.2.1)
      • v1.30.8---vmware.1-fips-vkr.1 (supported from Portworx version 3.3.0)
    • VMware Tanzu Kubernetes Grid Integrated Edition (TKGI):
      • TKGI version: 1.18.2-build.18, Kubernetes version: 1.27.11
      • TKGI version: 1.19.2-build, Kubernetes version: 1.28.11
      • TKGI version: 1.20.0-build.52, Kubernetes version: 1.29.6
    Google Anthos
    • Bare metal:
      • Anthos version: 1.28.500-gke.121, Kubernetes version: v1.28.8-gke.2000
      • Anthos version: 1.29.900-gke.180, Kubernetes version: v1.29.11-gke.300
      • Anthos version: 1.30.400-gke.133, Kubernetes version: v1.30.6-gke.300
      • Anthos version: 1.31.400-gke.110, Kubernetes version: v1.31.7-gke.1000
    • VMware:
      • Anthos version: 1.28.200-gke.111, vSphere version: 8.0, Kubernetes version: v1.28.4-gke.1400
      • Anthos version: 1.29.100-gke.248, vSphere version: 7.0.3 & 8.0, Kubernetes version: v1.29.4-gke.200
      • Anthos version: 1.30.400-gke.133, vSphere version: 7.0.3 & 8.0, Kubernetes version: v1.30.11-gke.700
      • Anthos version: 1.31.400-gke.110, vSphere version: 7.0.3 & 8.0.3, Kubernetes version: v1.31.7-gke.1000

    What to do next​

    You can install Portworx on the cloud or on-premises. Proceed to one of the following sections for Kubernetes and OpenShift install instructions.

    Last updated on