openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Merge pull request #97788 from openshift-cherrypick-robot/cherry-pick-97646-to-enterprise-4.17

Browse Source 
[enterprise-4.17] OSDOCS-15807 [NETOBSERV] Aditi check: DiscreteHeading
This commit is contained in:
Max Bridges
2025-08-19 14:24:55 -04:00
committed by GitHub
parent 76387af177 2b27a8e5b2
commit f99a672dc4
2 changed files with 5 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
observability/network_observability/network-observability-operator-release-notes.adoc
View File

@@ -470,8 +470,7 @@ You can configure the `FlowCollector` resource to collect information about the
==== Notable enhancements
The 1.5 release of the Network Observability Operator adds improvements and new capabilities to the {product-title} web console plugin and the Operator configuration.
[discrete]
[id="performance-enhancements-1.5"]
[id="performance-enhancements-1.5_{context}"]
===== Performance enhancements
* The `spec.agent.ebpf.kafkaBatchSize` default is changed from `10MB` to `1MB` to enhance eBPF performance when using Kafka.
+
@@ -480,8 +479,7 @@ The 1.5 release of the Network Observability Operator adds improvements and new
When upgrading from an existing installation, this new value is not set automatically in the configuration. If you monitor a performance regression with the eBPF Agent memory consumption after upgrading, you might consider reducing the `kafkaBatchSize` to the new value.
=====
[discrete]
[id="web-console-enhancements-1.5"]
[id="web-console-enhancements-1.5_{context}"]
===== Web console enhancements:
* There are new panels added to the *Overview* view for DNS and RTT: Min, Max, P90, P99.
@@ -493,8 +491,7 @@ When upgrading from an existing installation, this new value is not set automati
* There is enhanced visibility for the contents of the *Manage panels* and *Manage columns* pop-up windows.
* The Differentiated Services Code Point (DSCP) field for egress QoS is available for filtering QoS DSCP in the web console *Network Traffic* page.
[discrete]
[id="configuration-enhancements-1.5"]
[id="configuration-enhancements-1.5_{context}"]
===== Configuration enhancements:
* The `LokiStack` mode in the `spec.loki.mode` specification simplifies installation by automatically setting URLs, TLS, cluster roles and a cluster role binding, as well as the `authToken` value. The `Manual` mode allows more control over configuration of these settings.
@@ -572,7 +569,6 @@ You must switch your channel from `v1.0.x` to `stable` to receive the latest Ope
==== Notable enhancements
The 1.4 release of the Network Observability Operator adds improvements and new capabilities to the {product-title} web console plugin and the Operator configuration.
[discrete]
[id="web-console-enhancements-1.4_{context}"]
===== Web console enhancements:
@@ -585,7 +581,6 @@ The 1.4 release of the Network Observability Operator adds improvements and new
For more information, see xref:../../observability/network_observability/network-observability-overview.adoc#network-observability-dashboards_network-observability-overview[Network observability metrics dashboards] and xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-quickfilter_nw-observe-network-traffic[Quick filters].
[discrete]
[id="configuration-enhancements-1.4_{context}"]
===== Configuration enhancements:

5
observability/network_observability/network-observability-secondary-networks.adoc
View File

@@ -8,9 +8,8 @@ toc::[]
You can configure the Network Observability Operator to collect and enrich network flow data from secondary networks, such as SR-IOV and OVN-Kubernetes.
// Note to tech review:
// Is the existing SR-IOV example we have, "Configuring monitoring for SR-IOV interface traffic", an example of secondary network? If so, it is not through a VM, right?
// Is the existing SR-IOV example we have, "Configuring monitoring for SR-IOV interface traffic", an example of secondary network? If so, it is not through a VM, right?
[discrete]
[id="network-observability-secondary-network-prerequisites_{context}"]
== Prerequisites
* Access to an {product-title} cluster with an additional network interface, such as a secondary interface or an L2 network.
@@ -19,6 +18,6 @@ include::modules/network-observability-SRIOV-configuration.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources
*xref:../../networking/hardware_networks/configuring-sriov-device.adoc#cnf-creating-an-additional-sriov-network-with-vrf-plug-in_configuring-sriov-device[Creating an additional SR-IOV network attachment with the CNI VRF plugin].
* xref:../../networking/hardware_networks/configuring-sriov-device.adoc#cnf-creating-an-additional-sriov-network-with-vrf-plug-in_configuring-sriov-device[Configuring an SR-IOV network device]
include::modules/network-observability-virtualization-configuration.adoc[leveloffset=+1]