mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-06 15:46:57 +01:00
f154b76cf2
Fix incorrect range. https://docs.openshift.com/container-platform/4.16/networking/configuring-node-port-service-range.html
32 lines
1.3 KiB
Plaintext
32 lines
1.3 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * installing/install_config/configuring-firewall.adoc
|
|
|
|
:_mod-docs-content-type: REFERENCE
|
|
[id="network-flow-matrix_{context}"]
|
|
= {product-title} network flow matrix
|
|
|
|
The network flow matrix describes the ingress flows to {product-title} services.
|
|
The network information in the matrix is accurate for both bare-metal and cloud environments.
|
|
Use the information in the network flow matrix to help you manage ingress traffic.
|
|
You can restrict ingress traffic to essential flows to improve network security.
|
|
|
|
To view or download the raw CSV content, see link:https://raw.githubusercontent.com/openshift/openshift-docs/main/snippets/network-flow-matrix.csv[this resource].
|
|
|
|
Additionally, consider the following dynamic port ranges when managing ingress traffic:
|
|
|
|
* `9000-9999`: Host level services
|
|
* `30000-32767`: Kubernetes node ports
|
|
* `49152-65535`: Dynamic or private ports
|
|
|
|
[NOTE]
|
|
====
|
|
The network flow matrix describes ingress traffic flows for a base {product-title} installation. It does not describe network flows for additional components, such as optional Operators available from the Red Hat Marketplace. The matrix does not apply for Hosted-Control-Plane, MicroShift, or standalone clusters.
|
|
====
|
|
|
|
.Network flow matrix
|
|
[%header,format=csv]
|
|
|===
|
|
include::snippets/network-flow-matrix.csv[]
|
|
|===
|