Description of problem

There is no official documentation covering the general ingress and egress port requirements for HCP clusters. Customers are asking about which ports need to be opened for cluster communication, and there are no official docs to reference.

This is a documentation gap that affects all OpenShift versions.

Version-Release number of selected component (if applicable)

All versions

How reproducible

Always

Steps to Reproduce

Navigate to the OpenShift official documentation

Search for general ingress/egress port requirements

Attempt to find a comprehensive list of required ports and protocols for cluster operation

Actual results

No official documentation exists that covers the general ingress and egress port requirements for HCP clusters. Customers and support engineers have no authoritative reference to point to when configuring firewalls or answering questions about required network ports.

Expected results

Official documentation should exist that provides a comprehensive list of ingress and egress port requirements, including:

• Required ports and protocols for cluster communication
• Ports needed for ingress traffic (e.g., application routes, API server access)
• Ports needed for egress traffic (e.g., registry access, telemetry, cloud provider APIs)
• Any platform-specific port requirements

Additional info

This gap was identified through a customer question about port requirements. Without official documentation, customers must rely on tribal knowledge or incomplete community resources when configuring network security policies and firewall rules for their HCP deployments.

There are some ingress/egress port requirements documented under the KubeVirt provider specifically (Firewall and port requirements), but nothing is mentioned generically across providers.

Upstream docs for HCP networking requirements have been added and can serve as a reference for the official docs: HCP Networking Requirements