Skip to content

Commit 178cae0

Browse files
authored
Merge pull request #96885 from openshift-cherrypick-robot/cherry-pick-96415-to-enterprise-4.19
[enterprise-4.19] OSDOCS-15341 NETOBSERV 1.9.1 release notes
2 parents 597c130 + df0420a commit 178cae0

File tree

1 file changed

+19
-1
lines changed

1 file changed

+19
-1
lines changed

observability/network_observability/network-observability-operator-release-notes.adoc

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
:_mod-docs-content-type: ASSEMBLY
33
[id="network-observability-operator-release-notes"]
44
= Network Observability Operator release notes
5-
:context: network-observability-operator-release-notes-v1-9
5+
:context: network-observability-operator-release-notes-v1-9-1
66
include::_attributes/common-attributes.adoc[]
77

88
toc::[]
@@ -13,6 +13,24 @@ These release notes track the development of the Network Observability Operator
1313

1414
For an overview of the Network Observability Operator, see xref:../../observability/network_observability/network-observability-overview.adoc#dependency-network-observability[About Network Observability Operator].
1515

16+
[id="network-observability-operator-release-notes-1-9-1_{context}"]
17+
== Network Observability Operator 1.9.1
18+
The following advisory is available for the Network Observability Operator 1.9.1:
19+
20+
* link:https://access.redhat.com/errata/RHEA-2025:12024[2025:12024 Network Observability Operator 1.9.1]
21+
22+
[id="network-observability-operator-1-9-1-bug-fixes_{context}"]
23+
=== Bug fixes
24+
* 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*])
25+
26+
* 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*])
27+
28+
* 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*])
29+
30+
* 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*])
31+
32+
* 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*])
33+
1634
[id="network-observability-operator-release-notes-1-9_{context}"]
1735
== Network Observability Operator 1.9
1836
The following advisory is available for the Network Observability Operator 1.9:

0 commit comments

Comments
 (0)