Skip to content

Commit d6ae1e7

Browse files
authored
Merge pull request #76714 from jab-rh/rn-OSDOCS-10540
OSDOCS-10540: Add IPsec telemetry release note
2 parents 21e1576 + 3d6342b commit d6ae1e7

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

release_notes/ocp-4-16-release-notes.adoc

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -794,7 +794,6 @@ With this release, you can configure an {product-title} cluster on any on-premis
794794
For more information about this feature on bare-metal infrastructure, see xref:../installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc#nw-osp-services-external-load-balancer_ipi-install-installation-workflow[Services for a user-managed load balancer] in _Setting up the environment for an OpenShift installation_.
795795

796796
[id="ocp-4-16-detect-warning-for-iptables_{context}"]
797-
[id="ocp-4-16-detect-warning-for-iptables"]
798797
==== Detect and warning for iptables
799798
With this release, if you have pods in your cluster using `iptables` rules the following event message is given to warn against future deprecation:
800799
`This pod appears to have created one or more iptables rules. IPTables is deprecated and will no longer be available in RHEL 10 and later. You should consider migrating to another API such as nftables or eBPF.`
@@ -865,8 +864,13 @@ If you use the OVN-Kubernetes network plugin, you can configure the transit, joi
865864

866865
For more information about these configuration fields, see xref:../networking/cluster-network-operator.adoc#nw-operator-cr-cno-object_cluster-network-operator[Cluster Network Operator configuration object]. For more information about configuring the transit and join subnets on an existing cluster, see Configure OVN-Kubernetes internal IP address subnets.
867866

868-
//[id="ocp-4-16-registry_{context}"]
869-
//=== Registry
867+
[id="ocp-4-16-networking-ipsec-metrics_{context}"]
868+
==== IPsec telemetry
869+
870+
The Telemetry and the Insights Operator collects telemetry on IPsec connections. For more information, see xref:../support/remote_health_monitoring/showing-data-collected-by-remote-health-monitoring.adoc#showing-data-collected-from-the-cluster_showing-data-collected-by-remote-health-monitoring[Showing data collected by Telemetry].
871+
872+
[id="ocp-4-16-registry_{context}"]
873+
=== Registry
870874

871875
[id="ocp-4-16-storage_{context}"]
872876
=== Storage

0 commit comments

Comments
 (0)