mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
OSDOCS-17383 [NETOBSERV] Replace content in release-notes.adoc assembly with 1.10 modules
This commit is contained in:
Gwynne Monahan
committed by
openshift-cherrypick-robot
openshift-cherrypick-robot
parent
ea4b3fdbd1
commit
1a1b70ac05
@@ -3252,10 +3252,6 @@ Topics:
|
||||
Dir: network_observability
|
||||
Distros: openshift-enterprise,openshift-origin
|
||||
Topics:
|
||||
- Name: Network Observability Operator release notes 1.10
|
||||
File: network-observability-operator-release-notes-1-10
|
||||
#Keeping network-observability-operator-release-notes until all entries have been modularized.
|
||||
#Once all entire have been modularized, it will be updated with modules from 1-10 and these comments will be removed.
|
||||
- Name: Network Observability Operator release notes
|
||||
File: network-observability-operator-release-notes
|
||||
- Name: Network Observability Operator release notes archive
|
||||
|
||||
@@ -1,27 +0,0 @@
|
||||
//Network Observability Operator Release Notes
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="network-observability-operator-release-notes-1-10"]
|
||||
= Network Observability Operator release notes 1.10
|
||||
|
||||
:context: network-observability-operator-release-notes-v1-10
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
|
||||
toc::[]
|
||||
|
||||
With the Network Observability Operator, administrators can observe and analyze network traffic flows for {product-title} clusters.
|
||||
|
||||
These release notes track the development of the Network Observability Operator in the {product-title}.
|
||||
|
||||
For an overview of the Network Observability Operator, see xref:../../observability/network_observability/network-observability-overview.adoc#network-observability-overview[About Network Observability Operator].
|
||||
|
||||
include::modules/network-observability-operator-release-notes-1-10-advisory.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/network-observability-operator-release-notes-1-10-new-features-enhancements.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/network-observability-operator-release-notes-1-10-technology-preview-features.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/network-observability-operator-release-notes-1-10-removed-features.adoc[leveloffest=+1]
|
||||
|
||||
include::modules/network-observability-operator-release-notes-1-10-known-issues.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/network-observability-operator-release-notes-1-10-fixed-issues.adoc[leveloffset=+1]
|
||||
@@ -4,7 +4,7 @@
|
||||
= Network Observability Operator release notes
|
||||
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: network-observability-operator-release-notes-v1-9-1
|
||||
:context: network-observability-operator-release-notes
|
||||
|
||||
toc::[]
|
||||
|
||||
@@ -14,227 +14,14 @@ These release notes track the development of the Network Observability Operator
|
||||
|
||||
For an overview of the Network Observability Operator, see xref:../../observability/network_observability/network-observability-overview.adoc#network-observability-overview[About network observability].
|
||||
|
||||
////
|
||||
When all content in this assembly has been modularized:
|
||||
- move NETOSBERV 1.10 modules into this assembly
|
||||
- remove the network-observability-operator-release-notes-1-10.adoc file
|
||||
- update the _topic_map accordingly
|
||||
- update the addtl-release-notes.adoc file for each OCP version.
|
||||
include::modules/network-observability-operator-release-notes-1-10-advisory.adoc[leveloffset=+1]
|
||||
|
||||
This will meet migration requirements, simplify future updates, and remove the need to update addtle-release-notes with each NETOBSERV release.
|
||||
include::modules/network-observability-operator-release-notes-1-10-new-features-enhancements.adoc[leveloffset=+1]
|
||||
|
||||
Delete this comment block when all of that is done.
|
||||
////
|
||||
include::modules/network-observability-operator-release-notes-1-10-technology-preview-features.adoc[leveloffset=+1]
|
||||
|
||||
[id="network-observability-operator-release-notes-1-9-1_{context}"]
|
||||
== Network Observability Operator 1.9.1
|
||||
The following advisory is available for the Network Observability Operator 1.9.1:
|
||||
include::modules/network-observability-operator-release-notes-1-10-removed-features.adoc[leveloffest=+1]
|
||||
|
||||
* link:https://access.redhat.com/errata/RHEA-2025:12024[2025:12024 Network Observability Operator 1.9.1]
|
||||
include::modules/network-observability-operator-release-notes-1-10-known-issues.adoc[leveloffset=+1]
|
||||
|
||||
[id="network-observability-operator-1-9-1-bug-fixes_{context}"]
|
||||
=== Bug fixes
|
||||
* Before this update, network flows were not observed on {product-title} 4.15 due to an incorrect attach mode setting. This stopped users from monitoring network flows correctly, especially with certain catalogs. With this release, the default attach mode for {product-title} versions older than 4.16.0 is set to `tc`, so flows are now observed on {product-title} 4.15. (link:https://issues.redhat.com/browse/NETOBSERV-2333[*NETOBSERV-2333*])
|
||||
|
||||
* Before this update, if an IPFIX collector restarted, configuring an IPFIX exporter could lose its connection and stop sending network flows to the collector. With this release, the connection is restored, and network flows continue to be sent to the collector. (link:https://issues.redhat.com/browse/NETOBSERV-2315[*NETOBSERV-2315*])
|
||||
|
||||
* Before this update, when you configured an IPFIX exporter, flows without port information (such as ICMP traffic) were ignored, which caused errors in logs. TCP flags and ICMP data were also missing from IPFIX exports. With this release, these details are now included. Missing fields (like ports) no longer cause errors and are part of the exported data. (link:https://issues.redhat.com/browse/NETOBSERV-2307[*NETOBSERV-2307*])
|
||||
|
||||
* Before this update, the User Defined Networks (UDN) Mapping feature showed a configuration issue and warning on {product-title} 4.18 because the OpenShift version was incorrectly set in the code. This impacted the user experience. With this release, UDN Mapping now supports {product-title} 4.18 without warnings, making the user experience smooth. (link:https://issues.redhat.com/browse/NETOBSERV-2305[*NETOBSERV-2305*])
|
||||
|
||||
* Before this update, the expand function on the *Network Traffic* page had compatibility problems with {product-title} Console 4.19. This resulted in empty menu space when expanding and an inconsistent user interface. With this release, the compatibility problem in the `NetflowTraffic` part and `theme hook` is resolved. The side menu in the *Network Traffic* view is now properly managed, which improves how you interact with the user interface. (link:https://issues.redhat.com/browse/NETOBSERV-2304[*NETOBSERV-2304*])
|
||||
|
||||
[id="network-observability-operator-release-notes-1-9_{context}"]
|
||||
== Network Observability Operator 1.9
|
||||
The following advisory is available for the Network Observability Operator 1.9:
|
||||
|
||||
* link:https://access.redhat.com/errata/RHSA-2025:10020[Network Observability Operator 1.9]
|
||||
|
||||
[id="new-features-enhancements-1-9"]
|
||||
=== New features and enhancements
|
||||
|
||||
[id="user-defined-networks-with-network-observability_{context}"]
|
||||
==== User-defined networks with network observability
|
||||
With this release, xref:../../networking/multiple_networks/understanding-multiple-networks.adoc#understanding-multiple-networks[user-defined networks (UDN)] feature is generally available with network observability. When the `UDNMapping` feature is enabled in network observability, the *Traffic* flow table has a `UDN labels` column. You can filter logs on *Source Network Name* and *Destination Network Name* information.
|
||||
|
||||
[id="filter-flowlogs-at-ingestion_{context}"]
|
||||
==== Filter flowlogs at ingestion
|
||||
With this release, you can create filters to reduce the number of generated network flows and the resource usage of network observability components. The following filters can be configured:
|
||||
|
||||
* eBPF Agent filters
|
||||
* Flowlogs-pipeline filters
|
||||
|
||||
[id="ipsec-support_{context}"]
|
||||
==== IPsec support
|
||||
This update brings the following enhancements to network observability when IPsec is enabled on {product-title}:
|
||||
|
||||
* A new column named *IPsec Status* is displayed in the network observability *Traffic* flows view to show whether a flow was successfully IPsec-encrypted or if there was an error during encryption/decryption.
|
||||
|
||||
* A new dashboard showing the percentage of encrypted traffic is generated.
|
||||
|
||||
[id="network-observability-cli-1-9_{context}"]
|
||||
==== Network Observability CLI
|
||||
The following filtering options are now available for packets, flows, and metrics capture:
|
||||
|
||||
* Configure the ratio of packets being sampled by using the `--sampling` option.
|
||||
* Filter flows using a custom query by using the `--query` option.
|
||||
* Specify interfaces to monitor by using the `--interfaces` option.
|
||||
* Specify interfaces to exclude by using the `--exclude_interfaces` option.
|
||||
* Specify metric names to generate by using the `--include_list` option.
|
||||
|
||||
For more information, see xref:../../observability/network_observability/netobserv_cli/netobserv-cli-reference.adoc#network-observability-netobserv-cli-reference_netobserv-cli-reference[Network Observability CLI reference].
|
||||
|
||||
[id="notable-technical-changes-1-9_{context}"]
|
||||
=== Notable technical changes
|
||||
* The `NetworkEvents` feature in network observability 1.9 has been updated to work with the newer Linux kernel of {product-title} 4.19. This update breaks compatibility with older kernels. As a result, the `NetworkEvents` feature can only be used with {product-title} 4.19. If you are using this feature with network observability 1.8 and {product-title} 4.18, consider avoiding a network observability upgrade or upgrade to network observability 1.9 and {product-title} to 4.19.
|
||||
|
||||
* The `netobserv-reader` cluster role has been renamed to `netobserv-loki-reader`.
|
||||
|
||||
* Improved CPU performance of the eBPF agents.
|
||||
|
||||
[id="network-observability-technology-preview-1-9_{context}"]
|
||||
=== Technology Preview features
|
||||
Some features in this release are currently in Technology Preview. These experimental features are not intended for production use. Note the following scope of support on the Red Hat Customer Portal for these features:
|
||||
|
||||
link:https://access.redhat.com/support/offerings/techpreview[Technology Preview Features Support Scope]
|
||||
|
||||
[id="ebpf-manager-operator-with-network-observability_{context}"]
|
||||
==== eBPF Manager Operator with network observability
|
||||
|
||||
The eBPF Manager Operator reduces the attack surface and ensures compliance, security, and conflict prevention by managing all eBPF programs. Network observability can use the eBPF Manager Operator to load hooks. This eliminates the need to provide the eBPF Agent with privileged mode or additional Linux capabilities like `CAP_BPF` and `CAP_PERFMON`. The eBPF Manager Operator with network observability is only supported on 64-bit AMD architecture.
|
||||
|
||||
[id="network-observability-operator-CVE-1-9_{context}"]
|
||||
=== CVE
|
||||
|
||||
* link:https://access.redhat.com/security/cve/CVE-2025-26791[*CVE-2025-26791*]
|
||||
|
||||
[id="network-observability-operator-1-9-bug-fixes_{context}"]
|
||||
=== Bug fixes
|
||||
* Previously, when filtering by source or destination IP from the console plugin, using a Classless Inter-Domain Routing (CIDR) notation such as `10.128.0.0/24` did not work, returning results that should be filtered out. With this update, it is now possible to use a CIDR notation, with the results being filtered as expected. (link:https://issues.redhat.com/browse/NETOBSERV-2276[*NETOBSERV-2276*])
|
||||
|
||||
* Previously, network flows might have incorrectly identified the network interfaces in use, especially with a risk of mixing up `eth0` and `ens5`. This issue only occurred when the eBPF agents were configured as `Privileged`. With this update, it has been fixed partially, and almost all network interfaces are correctly identified. Refer to the known issues below for more details. (link:https://issues.redhat.com/browse/NETOBSERV-2257[*NETOBSERV-2257*])
|
||||
|
||||
* Previously, when the Operator checked for available Kubernetes APIs in order to adapt its behavior, if there was a stale API, this resulted in an error that prevented the Operator from starting normally. With this update, the Operator ignores error on unrelated APIs, logs errors on related APIs, and continues to run normally. (link:https://issues.redhat.com/browse/NETOBSERV-2240[*NETOBSERV-2240*])
|
||||
|
||||
* Previously, users could not sort flows by *Bytes* or *Packets* in the *Traffic* flows view of the Console plugin. With this update, users can sort flows by *Bytes* and *Packets*. (link:https://issues.redhat.com/browse/NETOBSERV-2239[*NETOBSERV-2239*])
|
||||
|
||||
* Previously, when configuring the `FlowCollector` resource with an IPFIX exporter, MAC addresses in the IPFIX flows were truncated to their 2 first bytes. With this update, MAC addresses are fully represented in the IPFIX flows. (link:https://issues.redhat.com/browse/NETOBSERV-2208[*NETOBSERV-2208*])
|
||||
|
||||
* Previously, some of the warnings sent from the Operator validation webhook could lack clarity on what needed to be done. With this update, some of these messages have been reviewed and amended to make them more actionable. (link:https://issues.redhat.com/browse/NETOBSERV-2178[*NETOBSERV-2178*])
|
||||
|
||||
* Previously, it was not obvious to figure out there was an issue when referencing a `LokiStack` from the `FlowCollector` resource, such as in case of typing error. With this update, the `FlowCollector` status clearly states that the referenced `LokiStack` is not found in that case. (link:https://issues.redhat.com/browse/NETOBSERV-2174[*NETOBSERV-2174*])
|
||||
|
||||
* Previously, in the console plugin *Traffic flows* view, in case of text overflow, text ellipses sometimes hid much of the text to be displayed. With this update, it displays as much text as possible. (link:https://issues.redhat.com/browse/NETOBSERV-2119[*NETOBSERV-2119*])
|
||||
|
||||
* Previously, the console plugin for network observability 1.8.1 and earlier did not work with the {product-title} 4.19 web console, making the *Network Traffic* page inaccessible. With this update, the console plugin is compatible and the *Network Traffic* page is accessible in network observability 1.9.0. (link:https://issues.redhat.com/browse/NETOBSERV-2046[*NETOBSERV-2046*])
|
||||
|
||||
* Previously, when using conversation tracking (`logTypes: Conversations` or `logTypes: All` in the `FlowCollector` resource), the *Traffic* rates metrics visible in the dashboards were flawed, wrongly showing an out-of-control increase in traffic. Now, the metrics show more accurate traffic rates. However, note that in `Conversations` and `EndedConversations` modes, these metrics are still not completely accurate as they do not include long-standing connections. This information has been added to the documentation. The default mode `logTypes: Flows` is recommended to avoid these inaccuracy. (link:https://issues.redhat.com/browse/NETOBSERV-1955[*NETOBSERV-1955*])
|
||||
|
||||
[id="network-observability-operator-1-9-known-issues_{context}"]
|
||||
=== Known issues
|
||||
* The user-defined network (UDN) feature displays a configuration issue and a warning when used with {product-title} 4.18, even though it is supported. This warning can be ignored. (link:https://issues.redhat.com/browse/NETOBSERV-2305[*NETOBSERV-2305*])
|
||||
|
||||
* In some rare cases, the eBPF agent is unable to appropriately correlate flows with the involved interfaces when running in `privileged` modes with several network namespaces. A large part of these issues have been identified and resolved in this release, but some inconsistencies remain, especially with the `ens5` interface. (link:https://issues.redhat.com/browse/NETOBSERV-2287[*NETOBSERV-2287*])
|
||||
|
||||
[id="network-observability-operator-release-notes-1-8-1_{context}"]
|
||||
== Network Observability Operator 1.8.1
|
||||
The following advisory is available for the Network Observability Operator 1.8.1:
|
||||
|
||||
* link:https://access.redhat.com/errata/RHSA-2025:3867[Network Observability Operator 1.8.1]
|
||||
|
||||
[id="network-observability-operator-CVE-1-8-1_{context}"]
|
||||
=== CVEs
|
||||
* link:https://access.redhat.com/security/cve/CVE-2024-56171[CVE-2024-56171]
|
||||
* link:https://access.redhat.com/security/cve/CVE-2025-24928[CVE-2025-24928]
|
||||
|
||||
[id="network-observability-operator-1-8-1-bug-fixes_{context}"]
|
||||
=== Bug fixes
|
||||
* This fix ensures that the *Observe* menu appears only once in future versions of {product-title}. (link:https://issues.redhat.com/browse/NETOBSERV-2139[*NETOBSERV-2139*])
|
||||
|
||||
[id="network-observability-operator-release-notes-1-8_{context}"]
|
||||
== Network Observability Operator 1.8.0
|
||||
The following advisory is available for the Network Observability Operator 1.8.0:
|
||||
|
||||
* link:https://access.redhat.com/errata/RHEA-2025:1940[Network Observability Operator 1.8.0]
|
||||
|
||||
[id="network-observability-operator-1.8.0-features-enhancements_{context}"]
|
||||
=== New features and enhancements
|
||||
|
||||
[id="network-observability-operator-pkt-xlat-1-8_{context}"]
|
||||
==== Packet translation
|
||||
You can now enrich network flows with translated endpoint information, showing not only the service but also the specific backend pod, so you can see which pod served a request.
|
||||
|
||||
For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-packet-translation-overview_nw-observe-network-traffic[Endpoint translation (xlat)] and xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-packet-translation_nw-observe-network-traffic[Working with endpoint translation (xlat)].
|
||||
|
||||
[id="network-observability-operator-OVN-observability-1-8_{context}"]
|
||||
==== OVN-Kubernetes networking events tracking
|
||||
|
||||
:FeatureName: OVN-Kubernetes networking events tracking
|
||||
include::snippets/technology-preview.adoc[]
|
||||
|
||||
You can now use network event tracking in network observability to gain insight into OVN-Kubernetes events, including network policies, admin network policies, and egress firewalls.
|
||||
|
||||
For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-viewing-network-events_nw-observe-network-traffic[Viewing network events].
|
||||
|
||||
[id="network-observability-operator-ebpf-perf-improvements-1-8_{context}"]
|
||||
==== eBPF performance improvements in 1.8
|
||||
|
||||
* Network observability now uses hash maps instead of per-CPU maps. This means that network flows data is now tracked in the kernel space and new packets are also aggregated there. The de-duplication of network flows can now occur in the kernel, so the size of data transfer between the kernel and the user spaces yields better performance. With these eBPF performance improvements, there is potential to observe a CPU resource reduction between 40% and 57% in the eBPF Agent.
|
||||
|
||||
[id="network-observability-cli-1-8_{context}"]
|
||||
==== Network Observability CLI
|
||||
|
||||
The following new features, options, and filters are added to the Network Observability CLI for this release:
|
||||
|
||||
* Capture metrics with filters enabled by running the `oc netobserv metrics` command.
|
||||
* Run the CLI in the background by using the `--background` option with flows and packets capture and running `oc netobserv follow` to see the progress of the background run and `oc netobserv copy` to download the generated logs.
|
||||
* Enrich flows and metrics capture with Machines, Pods, and Services subnets by using the `--get-subnets` option.
|
||||
* New filtering options available with packets, flows, and metrics capture:
|
||||
|
||||
** eBPF filters on IPs, Ports, Protocol, Action, TCP Flags and more
|
||||
** Custom nodes using `--node-selector`
|
||||
** Drops only using `--drops`
|
||||
** Any field using `--regexes`
|
||||
|
||||
For more information, see xref:../../observability/network_observability/netobserv_cli/netobserv-cli-reference.adoc#network-observability-netobserv-cli-reference_netobserv-cli-reference[Network Observability CLI reference].
|
||||
|
||||
[id="network-observability-operator-1-8-bug-fixes_{context}"]
|
||||
=== Bug fixes
|
||||
* Previously, the Network Observability Operator came with a "kube-rbac-proxy" container to manage RBAC for its metrics server. Since this external component is deprecated, it was necessary to remove it. It is now replaced with direct TLS and RBAC management through Kubernetes controller-runtime, without the need for a side-car proxy. (link:https://issues.redhat.com/browse/NETOBSERV-1999[*NETOBSERV-1999*])
|
||||
|
||||
* Previously in the {product-title} console plugin, filtering on a key that was not equal to multiple values would not filter anything. With this fix, the expected results are returned, which is all flows not having any of the filtered values. (link:https://issues.redhat.com/browse/NETOBSERV-1990[*NETOBSERV-1990*])
|
||||
|
||||
* Previously in the {product-title} console plugin with disabled Loki, it was very likely to generate a "Can't build query" error due to selecting an incompatible set of filters and aggregations. Now this error is avoided avoid by automatically disabling incompatible filters while still making the user aware of the filter incompatibility. (link:https://issues.redhat.com/browse/NETOBSERV-1977[*NETOBSERV-1977*])
|
||||
|
||||
* Previously, when viewing flow details from the console plugin, the ICMP info was always displayed in the side panel, showing "undefined" values for non-ICMP flows. With this fix, ICMP info is not displayed for non-ICMP flows. (link:https://issues.redhat.com/browse/NETOBSERV-1969[*NETOBSERV-1969*])
|
||||
|
||||
* Previously, the "Export data" link from the *Traffic flows* view did not work as intended, generating empty CSV reports. Now, the export feature is restored, generating non-empty CSV data. (link:https://issues.redhat.com/browse/NETOBSERV-1958[*NETOBSERV-1958*])
|
||||
|
||||
* Previously, it was possible to configure the `FlowCollector` with `processor.logTypes` `Conversations`, `EndedConversations` or `All` with `loki.enable` set to `false`, despite the conversation logs being only useful when Loki is enabled. This resulted in resource usage waste. Now, this configuration is invalid and is rejected by the validation webhook. (link:https://issues.redhat.com/browse/NETOBSERV-1957[*NETOBSERV-1957*])
|
||||
|
||||
* Configuring the `FlowCollector` with `processor.logTypes` set to `All` consumes much more resources, such as CPU, memory and network bandwidth, than the other options. This was previously not documented. It is now documented, and triggers a warning from the validation webhook. (link:https://issues.redhat.com/browse/NETOBSERV-1956[*NETOBSERV-1956*])
|
||||
|
||||
* Previously, under high stress, some flows generated by the eBPF agent were mistakenly dismissed, resulting in traffic bandwidth under-estimation. Now, those generated flows are not dismissed. (link:https://issues.redhat.com/browse/NETOBSERV-1954[*NETOBSERV-1954*])
|
||||
|
||||
* Previously, when enabling the network policy in the `FlowCollector` configuration, the traffic to the Operator webhooks was blocked, breaking the `FlowMetrics` API validation. Now traffic to the webhooks is allowed. (link:https://issues.redhat.com/browse/NETOBSERV-1934[*NETOBSERV-1934*])
|
||||
|
||||
* Previously, when deploying the default network policy, namespaces `openshift-console` and `openshift-monitoring` were set by default in the `additionalNamespaces` field, resulting in duplicated rules. Now there is no additional namespace set by default, which helps avoid getting duplicated rules.(link:https://issues.redhat.com/browse/NETOBSERV-1933[*NETOBSERV-1933*])
|
||||
|
||||
* Previously from the {product-title} console plugin, filtering on TCP flags would match flows having only the exact desired flag. Now, any flow having at least the desired flag appears in filtered flows. (link:https://issues.redhat.com/browse/NETOBSERV-1890[*NETOBSERV-1890*])
|
||||
|
||||
* When the eBPF agent runs in privileged mode and pods are continuously added or deleted, a file descriptor (FD) leak occurs. The fix ensures proper closure of the FD when a network namespace is deleted. (link:https://issues.redhat.com/browse/NETOBSERV-2063[*NETOBSERV-2063*])
|
||||
|
||||
* Previously, the CLI agent `DaemonSet` did not deploy on master nodes. Now, a toleration is added on the agent `DaemonSet` to schedule on every node when taints are set. Now, CLI agent `DaemonSet` pods run on all nodes. (link:https://issues.redhat.com/browse/NETOBSERV-2030[*NETOBSERV-2030*])
|
||||
|
||||
* Previously, the *Source Resource* and *Source Destination* filters autocomplete were not working when using Prometheus storage only. Now this issue is fixed and suggestions displays as expected. (link:https://issues.redhat.com/browse/NETOBSERV-1885[*NETOBSERV-1885*])
|
||||
|
||||
* Previously, a resource using multiple IPs was displayed separately in the *Topology* view. Now, the resource shows as a single topology node in the view. (link:https://issues.redhat.com/browse/NETOBSERV-1818[*NETOBSERV-1818*])
|
||||
|
||||
* Previously, the console refreshed the *Network traffic* table view contents when the mouse pointer hovered over the columns. Now, the display is fixed, so row height remains constant with a mouse hover. (link:https://issues.redhat.com/browse/NETOBSERV-2049[*NETOBSERV-2049*])
|
||||
|
||||
[id="network-observability-operator-1-8-known-issues_{context}"]
|
||||
=== Known issues
|
||||
|
||||
* If there is traffic that uses overlapping subnets in your cluster, there is a small risk that the eBPF Agent mixes up the flows from overlapped IPs. This can happen if different connections happen to have the exact same source and destination IPs and if ports and protocol are within a 5 seconds time frame and happening on the same node. This should not be possible unless you configured secondary networks or UDN. Even in that case, it is still very unlikely in usual traffic, as source ports are usually a good differentiator. (link:https://issues.redhat.com/browse/NETOBSERV-2115[*NETOBSERV-2115*])
|
||||
|
||||
* After selecting a type of exporter to configure in the `FlowCollector` resource `spec.exporters` section from the {product-title} web console form view, the detailed configuration for that type does not show up in the form. The workaround is to configure directly the YAML. (link:https://issues.redhat.com/browse/NETOBSERV-1981[*NETOBSERV-1981*])
|
||||
include::modules/network-observability-operator-release-notes-1-10-fixed-issues.adoc[leveloffset=+1]
|
||||
Reference in New Issue
Block a user