mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-07 00:48:01 +01:00
be8a6929c7
ref config updates Adding generated YAML + modules from the RDS Reorganizing TOC Adding latest RDS updates RDS doc updates RDS YAML updates Shanes review latest updates + new components overview diagram David J's review comments CCS attributes update Ian's review comments adding Hari's deviations update updating 4.14 link URLs Generalizes scope and deviation topics for RAN and Core updates for RDS prod version update deviations wording Updating deviation and scope topics consolidate dev and scope topics + intro Adding link to ztp-site-generate procedure typo final changes for RDS typos Ian's comments update for RDS terminology remove core CRs note add GH core CRs link
29 lines
1.5 KiB
Plaintext
29 lines
1.5 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * telco_ref_design_specs/ran/telco-core-ref-components.adoc
|
|
|
|
:_mod-docs-content-type: REFERENCE
|
|
[id="telco-core-cluster-network-operator_{context}"]
|
|
= Cluster Network Operator (CNO)
|
|
|
|
New in this release::
|
|
|
|
Not applicable.
|
|
|
|
Description::
|
|
|
|
The CNO deploys and manages the cluster network components including the default OVN-Kubernetes network plugin during {product-title} cluster installation. It allows configuring primary interface MTU settings, OVN gateway modes to use node routing tables for pod egress, and additional secondary networks such as MACVLAN.
|
|
+
|
|
In support of network traffic segregation, multiple network interfaces are configured through the CNO. Traffic steering to these interfaces is configured through static routes applied by using the NMState Operator. To ensure that pod traffic is properly routed, OVN-K is configured with the `routingViaHost` option enabled. This setting uses the kernel routing table and the applied static routes rather than OVN for pod egress traffic.
|
|
+
|
|
The Whereabouts CNI plugin is used to provide dynamic IPv4 and IPv6 addressing for additional pod network interfaces without the use of a DHCP server.
|
|
|
|
Limits and requirements::
|
|
|
|
* OVN-Kubernetes is required for IPv6 support.
|
|
* Large MTU cluster support requires connected network equipment to be set to the same or larger value.
|
|
|
|
Engineering considerations::
|
|
* Pod egress traffic is handled by kernel routing table with the `routingViaHost` option. Appropriate static routes must be configured in the host.
|
|
|