Skip to main content
Version: 3.2

Prerequisites for OCP on bare metal

Environment Prerequisites

The minimum supported size for a Portworx cluster is three nodes. Each node must meet the following hardware, software, and network requirements:

Hardware
CPU4 cores minimum, 8 cores recommended
RAM4GB minimum, 8GB recommended
Disk
  • /var
  • /opt
  • 2GB free
  • 3GB free
Backing drive8GB (minimum required)
128 GB (minimum recommended)
Operating system root partition64 GB is the minimum required size for the root filesystem which contains the operating system
128 GB minimum recommended
Storage drivesStorage drives must be unmounted block storage: raw disks, drive partitions, LVM, or cloud block storage.
Network connectivityBandwidth:
  • 10 Gbps recommended
  • 1 Gbps minimum

Latency requirements for synchronous replication: less than 10ms between nodes in the cluster
Node typeVirtual machine (VM)
Open ports neededPortworx requires different open ports depending on how it's installed:
  • Portworx on OpenShift 4+ requires open TCP ports at 17001-17020 and an open UDP port at 17002.
  • Telemetry components require the following open ports: 9024, 12001, and 12002.
    • If you are on Portworx version 2.13.7 and older, open port 9024 for telemetry.
    • If you are on Portworx version 2.13.8 and newer, use port 9029 for telemetry.
    Ensure you are running Portworx Operator version 23.7.0 and higher to configure this port for Telemetry.
  • Portworx also requires an open KVDB port. For example, if you're using etcd externally, open port 2379.
  • If you intend to use Portworx with sharedv4 volumes, you may need to open your NFS ports.
Domain AllowlistingFor environments with locked down network connectivity, Portworx requires different domains to be allowlisted depending on how it's installed:
    Telemetry requires the following domains to be allowlisted:
  • pxessentials.portworx.com:443,
  • register.cloud-support.purestorage.com:443, and
  • rest.cloud-support.purestorage.com:443
Software
Linux kernel and distroKernel version 3.10 or greater.
To check if your Linux distro and kernel are supported, see Supported Kernels.
Key-value storePortworx 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 of using your own KVDB, refer to KVDB for Portworx for details on recommendations for installing and configuring a KVDB cluster.
Disable swapPlease disable swap on all nodes that will run the Portworx software. Ensure that the swap device is not automatically mounted on server reboot.

Portworx network requirements

Portworx runs as a pod in a Kubernetes cluster and uses specific ports for communication, data transfer, and telemetry.

note

Portworx also requires the following ports:

  • An open KVDB port. For example, if you're using etcd externally, open port 2379.
  • An open UDP port at 17002.
OpenShiftDescription
17001Portworx management port [REST]
17002Portworx node-to-node port [gossip]/UDP
17003Portworx storage data port
17004Portworx namespace [RPC]
17009Portworx node-to-node communication port [gRPC]
17010Portworx namespace driver [gRPC]
17011Portworx diags server port [gRPC]
17015Portworx kvdb peer-to-peer port [gRPC]
17016Portworx kvdb client service [gRPC]
17018Portworx gRPC SDK gateway [REST]
17019Portworx health monitor [REST]
17021Telemetry log uploader
20002Telemetry phone home

Portworx Enterprise supported versions

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

TypeSupported Versions
Red Hat OpenShift
  • OpenShift version: 4.13, verified up to 4.13.52, Kubernetes version: 1.26
  • OpenShift version: 4.14, verified up to 4.14.38, Kubernetes version: 1.27
  • OpenShift version: 4.15, verified up to 4.15.36, Kubernetes version: 1.28
  • OpenShift version: 4.16, verified up to 4.16.17, Kubernetes version: 1.29
  • OpenShift version: 4.17, verified up to 4.17.1, Kubernetes version: 1.30
  • Supports both bare metal and VM