OSDOCS-14862 NETOBSERV 1.9 Features, Bugs, Known Issues #94440
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -2,7 +2,7 @@ | |||||
| :_mod-docs-content-type: ASSEMBLY | ||||||
| [id="network-observability-operator-release-notes"] | ||||||
| = Network Observability Operator release notes | ||||||
| :context: network-observability-operator-release-notes-v1-9 | ||||||
| include::_attributes/common-attributes.adoc[] | ||||||
|
|
||||||
| toc::[] | ||||||
|
|
@@ -13,6 +13,104 @@ 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#dependency-network-observability[About Network Observability Operator]. | ||||||
|
|
||||||
| [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. | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| You can configure the following filters: | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| * 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: | ||||||
|
|
||||||
| * Track IPsec using `--enable_ipsec` | ||||||
|
Member
There was a problem hiding this comment. I wonder how this would look if you reformatted to something like
Suggested change
Technically this is how you'd do definition lists (https://www.ibm.com/docs/en/ibm-style?topic=format-lists), but I don't what you've written is 100% a definition list. Just a thought.
Contributor
Author
There was a problem hiding this comment. Appreciate the thought. The format is how it has been done since before I joined this team, so for now I'd prefer to keep it consistent. I'll make a note of it though for something to consider for the refactoring. Thanks!
Contributor
There was a problem hiding this comment. I agree with Steven here and think this needs to be updated if not for this release for future. If you aren't going to use the definition list these at least need nouns after the |
||||||
| * Value that determines the ratio of packets being sampled using `--sampling` | ||||||
| * Filter flows using a custom query using `--query` | ||||||
| * A comma separated list of interfaces to monitor using `--interfaces` | ||||||
| * A comma separated list of interfaces to exclude using `--exclude_interfaces` | ||||||
| * A comma separated list of metric names to generate using `--include_list` | ||||||
|
|
||||||
| 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 upgrading Network Observability to 1.9 and {product-title} to 4.19. | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| * The `netobserv-reader` `clusterrole` has been renamed to `netobserv-loki-reader`. | ||||||
|
Contributor
There was a problem hiding this comment. What are these parameters, fields, values, CR? Can you add nouns to help the user understand what these are? |
||||||
|
|
||||||
| * 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: | ||||||
|
|
||||||
|
Contributor
There was a problem hiding this comment. 69-71 seem redundant to me if you are going to use the TP snippet. |
||||||
| 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 | ||||||
|
|
||||||
| :FeatureName: eBPF Manager Operator with Network Observability | ||||||
| include::snippets/technology-preview.adoc[] | ||||||
|
|
||||||
| 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. | ||||||
gwynnemonahan marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
|
||||||
| [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*]) | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| * 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, such as when not mentioning exactly which feature causes the warning, or 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*]) | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| * 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 100% accurate as they don't include long-standing connections. This information has been added to the documentation. The default mode `logTypes: Flows`, is recommended to avoid this kind of inaccuracy. (link:https://issues.redhat.com/browse/NETOBSERV-1955[*NETOBSERV-1955*]) | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
gwynnemonahan marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
| [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*]) | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| [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: | ||||||
|
|
||||||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.