Enable IPv6 with Portworx

Portworx Documentation has moved to https://docs.portworx.com

Portworx Enterprise version 2.13 has reached end of life and end of extended maintenance. Refer to the release support policy doc here.
Upgrade to the latest version of Portworx Enterprise for continued support. Documentation for the latest version of Portworx Enterprise can be found here.

Supported configurations

IPv6 is supported by Portworx in the following configurations:

Operating system	Kubernetes version	Portworx configuration
CentOS 7.9 Kernel: 3.10.0-1160.53.1	1.23.0	Portworx Operator based installation Dual network - Management and Data traffic on a separate network Air-gapped with all required images pushed to an internal registry
CentOS 7.6 Kernel: 5.7.12-1	1.20.0	Portworx Operator based installation Single network - Management and Data traffic on a same network Air-gapped with all required images pushed to an internal registry
Ubuntu 18.04.4 Kernel: v5.3	1.23.0	Portworx Operator based installation Single network - Management and Data traffic on a same network Air-gapped with all required images pushed to an internal registry

Supported features

Portworx supports the following features with IPv6:

All basic features of Portworx
Prometheus monitoring
Autopilot

Unsupported features

Portworx does not support the following features with IPv6:

Portworx installation with mixed mode (IPv4 & IPv6)
Portworx installation with Cloud Drives
Portworx installation with proxy
PX-Central License Server
PX-Backup
Asynchronous and Synchronous disaster recovery (DR)
Telemetry

Enable IPv6 support

To enable IPv6 support, perform the following steps:

Specify your internal registry’s Portworx operator image path in your Portworx operator spec. Replace the line image: portworx/px-operator:<version_number> in the generated Portworx operator spec with the path to your internal registry operator image. For example:
```
image: <image_registry_hostname>/<repo_name>/<image_name>:<tag>
```
If your internal registry is password protected, create a secret to store the credentials, then specify the internal registry access info in the Portworx Storage Cluster spec. For example:
```
imagePullSecret: <secret_name>
customImageRegistry: <image_registry_hostname>/<repo_name>
```

Specify the oci-monitor path in the internal registry. For example:

spec:
  image: <image_registry_hostname>/<repo_name>/<image_name>:<tag>

For dual network deployments, specify network configuration. For example:

  network:
    dataInterface: <interface_name_for_data_traffic>
    mgmtInterface: <interface_name_for_mgmt_traffic>

Install Portworx on Kubernetes via Helm

Tune performance