OCP Network Prerequisites
Portworx network requirements
Portworx runs as a pod in a Kubernetes cluster and uses specific ports for communication, data transfer, and telemetry.
- East-to-west
- Inbound
- Outbound
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.
OpenShift | Description |
---|---|
17001 | Portworx management port [REST] |
17002 | Portworx node-to-node port [gossip]/UDP |
17003 | Portworx storage data port |
17004 | Portworx namespace [RPC] |
17009 | Portworx node-to-node communication port [gRPC] |
17010 | Portworx namespace driver [gRPC] |
17011 | Portworx diags server port [gRPC] |
17015 | Portworx kvdb peer-to-peer port [gRPC] |
17016 | Portworx kvdb client service [gRPC] |
17018 | Portworx gRPC SDK gateway [REST] |
17019 | Portworx health monitor [REST] |
17021 | Telemetry log uploader |
20002 | Telemetry phone home |
OpenShift | Description |
---|---|
17001 | Portworx management port [REST] |
17018 | Portworx gRPC SDK gateway [REST] |