Network ports

Certain network ports will need to be open for both ingress and egress for the deployment of BMC Helix Platform products.  Within the cluster, each pod has open ports to communicate with each other and with persistent storage.

Important

Ports are not configurable.

The following ports are required for BMC Helix Platform:

DescriptionPortFlow
Load balancer/ingress controller443Incoming requests from outside the load balancer and Kubernetes cluster.
Third-party networks, for example LDAP and SAMLPort to be configured by the applicationInbound from the K8 cluster to the third-party application.
Kibana user interface5601

Inbound from the K8 cluster to Kibana.

Important

The traffic to Kibana ports is routed from the Load Balancer on port 443 to the Ingress controller. As the Ingress controller decides the internal routing of the traffic, the Kibana ports should be open in the Kubernetes cluster.


Network ports for BMC Helix Operations Management

In addition to the ports required for BMC Helix Platform, the following ports are required for BMC Helix Operations Management:

DescriptionPortFlow

BMC Discovery 

443

Inbound from the K8 cluster to BMC Discovery .

BMC Discovery communication

25030 through 25033

Inbound from the K8 cluster to BMC Discovery.

The following image shows the network ports required for a BMC Helix Operations Management deployment:



Network ports for BMC Helix Continuous Optimization

In addition to the ports required for BMC Helix Platform, the following ports are required for BMC Helix Continuous Optimization:

DescriptionPortFlow

BMC Discovery 

443

Inbound from the K8 cluster to tBMC Discovery.

BMC Discovery communication

25030 through 25033

Inbound from the K8 cluster toBMC Discovery.

The following image shows the network ports required for a BMC Helix Continuous Optimization deployment:

Was this page helpful? Yes No Submitting... Thank you

Comments