1.3.13. Networking
- MetalLB Operator status reporting
You can now use enhanced MetalLB Operator reporting features to view real-time operational data for IP address allocation and Border Gateway Protocol (BGP) connectivity. Previously, viewing this information required manual log inspection across multiple controllers. With this release, you can monitor your network health and resolve connectivity issues directly through the following custom resources:
-
IPAddressPool: Monitor cluster-wide IP address allocation through thestatusfield to track usage and prevent address exhaustion. -
ServiceBGPStatus: Verify which service IP addresses are announced to specific BGP peers to ensure correct route advertisements. BGPSessionStatus: Check the real-time state of BGP and Bidirectional Forwarding Detection sessions to quickly identify connectivity drops.For more information, see Monitoring MetalLB configuration status.
-
- Applying unassisted holdover for boundary clocks and time synchronous clocks
OpenShift Container Platform 4.20 introduced unassisted holdover for boundary clocks and time synchronous clocks as a Technology Preview feature. This feature is now Generally Available (GA).
For more information, see Applying unassisted holdover for boundary clocks and time slave clocks.
- SR-IOV Operator supports ARM architecture
- The Single Root I/O Virtualization (SR-IOV) Operator can now communicate with ARM hardware. You can now complete tasks such as configure network cards that are already plugged into an ARM server and use these cards in your applications. For instructions on how to search for ARM hardware that the SR-IOV Operator supports, see About Single Root I/O Virtualization (SR-IOV) hardware networks.
- Support for Red Hat OpenShift Service Mesh version 3.2
- OpenShift Container Platform 4.21 updates Service Mesh to version 3.2. This version update incorporates essential CVE fixes and ensures that your OpenShift Container Platform instances receive the latest fixes, features, and enhancements. See the Service Mesh 3.2 release notes for more information.
- PTP Operator introduces GNSS-to-NTP failover for high-precision timing
With this release, the PTP Operator introduces an active GNSS-to-NTP failover configuration to ensure time synchronization continuity in environments requiring extremely high time accuracy.
When the primary Global Navigation Satellite System (GNSS) signal is lost or compromised, for example because of satellite jamming, the system automatically fails over to Network Time Protocol (NTP) to maintain time accuracy. When the GNSS signal is restored, the system automatically recovers back to using GNSS as the primary time source.
This feature is particularly important in telco environments that require high precision time synchronization with built-in redundancy. To enable GNSS to NTP failover, you configure the
PtpConfigresource with thentpfailoverplugin enabled and configure bothchronydandts2phcsettings.For more information, see Configuring GNSS failover to NTP for time synchronization continuity.
- Network policies for additional namespaces
- With this release, OpenShift Container Platform continues to deploy Kubernetes network policies to additional system namespaces to control ingress and egress traffic. It is anticipated that future releases might include network policies for additional system namespaces and Red Hat Operators.
- Ingress network flow analysis with the commatrix plugin
-
With this release, you can use the
commatrixplugin to generate ingress network flow data from your cluster. You can also use the plugin to identify any differences between open ports on the host and expected ingress flows for your environment.
For more information, see Ingress network flow analysis with the commatrix plugin
- Configure the dnsRecordsType parameter (Technology preview)
-
During cluster installation, you can specify the
dnsRecordsTypeparameter in theinstall-config.yamlfile to set if the internal DNS service or an external source provides the necessary records forapi,api-int, andingressDNS records. For more information about DNS requirements, see User-provisioned DNS requirements.