Skip to content

Commit b9888eb

Browse files
gwynnemonahangwynnemonahan
committed
OSDOCS-19149 [NETOBSERV] 1.12 Release Notes
1 parent 3c13914 commit b9888eb

7 files changed

Lines changed: 185 additions & 10 deletions

‎modules/network-observability-operator-release-notes-1-12-advisory.adoc‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
// Module included in the following assemblies:
2+
// * network_observability/network-observability-release-notes.adoc
3+
4+
:_mod-docs-content-type: REFERENCE
5+
[id="network-observability-operator-release-notes_{context}"]
6+
= Network Observability Operator 1.12 advisory
7+
8+
[role="_abstract"]
9+
You can review the advisory for Network Observability Operator 1.12 release.
10+
11+
* link:https://access.redhat.com/errata/RHSA-2026:24473[RHSA-2026:24473 Network Observability Operator 1.12]

‎modules/network-observability-operator-release-notes-1-12-fixed-issues.adoc‎

Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
// Module included in the following assemblies:
2+
// * network_observability/network-observability-release-notes.adoc
3+
4+
:_mod-docs-content-type: REFERENCE
5+
[id="network-observability-operator-release-notes-1-12-fixed-issues_{context}"]
6+
= Network Observability Operator 1.12 fixed issues
7+
8+
[role="_abstract"]
9+
The Network Observability Operator 1.12 release contains several fixed issues that improve performance, system status reporting, and user experience.
10+
11+
Consistent FlowCollector pipeline status::
12+
Before this update, changes to the sampling field caused an inconsistency in the `FlowCollector` resource status. As a consequence, you could see conflicting statuses across pipeline components.
13+
+
14+
With this release, status reporting is made consistent across all components. As a result, the reliability of the pipeline status indicator is improved.
15+
+
16+
link:https://issues.redhat.com/browse/NETOBSERV-2375[NETOBSERV-2375]
17+
18+
Fixed `--help` flag processing in netobserv-cli::
19+
Before this update, the `--help` flag was ignored when placed after other command flags in the Network Observability CLI. As a consequence, running commands such as `oc netobserv flows --interfaces=br-ex --max-time=10s --help` executed the flow collection instead of displaying the help page.
20+
+
21+
With this release, the `--help` flag is recognized regardless of its position in the command. As a result, you can now display help information by placing the `--help` flag anywhere in your command arguments.
22+
+
23+
link:https://issues.redhat.com/browse/NETOBSERV-2617[NETOBSERV-2617]
24+
25+
Improved visibility of DNS names warning messages::
26+
Before this update, the **DNS names** graph repeatedly displayed a warning message on every refresh when running in a Prometheus-only configuration. As a consequence, the persistent warning message covered other dashboard elements.
27+
+
28+
With this release, the warning message is only displayed during the initial data load and does not overlay other content. As a result, interface clarity is improved when navigating the dashboard.
29+
+
30+
link:https://issues.redhat.com/browse/NETOBSERV-2618[NETOBSERV-2618]
31+
32+
Prometheus enabled by default in FlowCollector configurations::
33+
Before this update, the default setting for Prometheus metrics was unassigned during `FlowCollector` custom resource creation. As a consequence, you had to manually ensure that metrics collection was active to query accurate flow data.
34+
+
35+
With this release, the default value for Prometheus metrics collection in the `FlowCollector` configuration is set to `true`. As a result, the deployment process is simplified and flow metrics are collected automatically.
36+
+
37+
link:https://issues.redhat.com/browse/NETOBSERV-2620[NETOBSERV-2620]
38+
39+
Usage examples added to CLI subcommand help text::
40+
Before this update, the `help` subcommands for the Network Observability CLI lacked syntax examples. As a consequence, understanding how to construct complex filtering and capture commands required additional research.
41+
+
42+
With this release, clear examples are included in the subcommand help outputs. As a result, the usability and discoverability of the CLI features are enhanced.
43+
+
44+
link:https://issues.redhat.com/browse/NETOBSERV-2646[NETOBSERV-2646]
45+
46+
Corrected latency formatting for values above one second::
47+
Before this update, flow durations and network latencies greater than one second were improperly formatted as milliseconds. As a consequence, donut graphs and latency metrics displayed confusing or inaccurate time designations.
48+
+
49+
With this release, the duration formatting function handles values greater than one millisecond accurately using decimal seconds. As a result, you can view precise network latency values in console charts.
50+
+
51+
link:https://issues.redhat.com/browse/NETOBSERV-2669[NETOBSERV-2669]
52+
53+
Improved FlowCollector status reporting when eBPF pods are absent::
54+
Before this update, the `FlowCollector` resource reported a status of `Ready` even when a restrictive `nodeSelector` prevented any eBPF agent pods from deploying. As a consequence, the system status misrepresented the health of the agent layer.
55+
+
56+
With this release, the Operator checks for a zero-pod deployment count. As a result, the `FlowCollector` CR now correctly identifies when zero eBPF pods are active, improving cluster error diagnostics.
57+
+
58+
link:https://issues.redhat.com/browse/NETOBSERV-2674[NETOBSERV-2674]
59+
60+
Optimized field exports for OpenTelemetry exporters::
61+
Before this update, the OpenTelemetry exporter processed missing or null keys as non-null data. As a consequence, unpopulated `metadata` fields were exported to log streams, which increased storage usage and cluttered telemetry files.
62+
+
63+
With this release, the OpenTelemetry exporter filters out null or unrelated fields, exporting only keys that belong to explicitly enabled features. As a result, exported log sizes are reduced and data efficiency is improved.
64+
+
65+
link:https://issues.redhat.com/browse/NETOBSERV-2705[NETOBSERV-2705]
66+
67+
Added sampling probability fields to IPFIX exports::
68+
Before this update, Internet Protocol Flow Information Export (IPFIX) record exports omitted per-flow sampling information. As a consequence, data exports failed to comply with the standard IPFIX specifications for `samplingProbability` usage.
69+
+
70+
With this release, the exporter includes sampling probability details within the IPFIX packet metadata. As a result, exported OpenTelemetry data matches industry compliance standards.
71+
+
72+
link:https://issues.redhat.com/browse/NETOBSERV-2706[NETOBSERV-2706]
73+
74+
Fixed TLS volume name conflicts on OpenTelemetry exporters::
75+
Before this update, configuring TLS certificates on OpenTelemetry exporters generated an invalid volume name format. As a consequence, the `apiserver` rejected the underlying Flow-logs Pipeline deployment specification, causing the pipeline pod to fail during initialization.
76+
+
77+
With this release, the Operator ensures valid volume names are generated when handling TLS attributes. As a result, enabling TLS on your OpenTelemetry exporters no longer interferes with pipeline pod lifecycles.
78+
+
79+
link:https://issues.redhat.com/browse/NETOBSERV-2707[NETOBSERV-2707]
80+
81+
Improved pod-to-pod flow filter rule matching for asymmetric CIDR rules::
82+
Before this update, the default flow filter action was not enforced when a network flow failed to match both a CIDR rule and its corresponding `peerCIDR` rule identically. As a consequence, unexpected acknowledgment-only, `ACK`, flows bypass filtering restrictions inside the pod network.
83+
+
84+
With this release, when a network flow matches a designated CIDR rule but fails the `peerCIDR` pairing, the default filtering action is correctly applied. As a result, traffic blocking and network rule isolation are handled more securely.
85+
+
86+
link:https://issues.redhat.com/browse/NETOBSERV-2755[NETOBSERV-2755]

‎modules/network-observability-operator-release-notes-1-12-known-issues.adoc‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
// Module included in the following assemblies:
2+
// * network_observability/network-observability-release-notes.adoc
3+
4+
:_mod-docs-content-type: REFERENCE
5+
[id="network-observability-operator-release-notes-1-12-known-issues_{context}"]
6+
= Network Observability Operator 1.12 known issues
7+
8+
[role="_abstract"]
9+
The following known issues affect the Network Observability Operator 1.12 release.
10+
11+
Operator fails to start when custom web console logos are configured::
12+
When you configure custom product logos in the `Console.operator.openshift.io` resource using the `spec.customization.logos` field, the Network Observability Operator pod fails to start during installation. The Operator incorrectly reports a validation error indicating that both `logos` and the deprecated `customLogoFile` fields are set, even though only `logos` is configured.
13+
+
14+
To work around this problem, manually enable the Network Observability Operator {product-title} web console plugin by adding `netobserv-plugin-static` to the `spec.plugins` list in the `Console` cluster resource, or by enabling the plugin through the web console under *Administration* -> *Cluster Settings* -> *Configuration* -> *Console* -> *Console plugins*.
15+
+
16+
link:https://issues.redhat.com/browse/NETOBSERV-2767[NETOBSERV-2767]

‎modules/network-observability-operator-release-notes-1-12-new-features-enhancements.adoc‎

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
// Module included in the following assemblies:
2+
// * network_observability/network-observability-release-notes.adoc
3+
4+
:_mod-docs-content-type: REFERENCE
5+
[id="network-observability-operator-release-notes-1-12-new-features-enhancements_{context}"]
6+
= Network Observability Operator 1.12 new features and enhancements
7+
8+
[role="_abstract"]
9+
The Network Observability Operator 1.12 release introduces non-decrypting TLS metadata tracking, Kafka message compression options, automated secondary network indexing, and expanded web console compatibility for {product-title} clusters.
10+
11+
Transport Layer Security traffic metadata tracking::
12+
The Network Observability Operator can now capture and analyze Transport Layer Security (TLS) metadata from network flows without decrypting traffic. By extracting handshake details from `ClientHello` and `ServerHello` messages, the Operator provides visibility into encryption protocols while maintaining data privacy.
13+
+
14+
The following key benefits include:
15+
+
16+
* Security risk detection: Identify workloads using deprecated TLS versions (1.0, 1.1) or weak cipher suites.
17+
* Compliance auditing: Audit TLS configurations to meet regulatory requirements through metric aggregation and dashboard visualization.
18+
* Security posture assessment: Visualize encrypted network traffic with lock icons in the *Topology* view and identify unencrypted communications across your cluster.
19+
* Configure Prometheus alerts to automatically report insecure or non-compliant TLS configurations.
20+
+
21+
To use this feature, enable `TLSTracking` in the `spec.agent.ebpf.features` list of the `FlowCollector` custom resource (CR).
22+
23+
Support for Kafka compression::
24+
Message compression configuration is now available when using Kafka to scale network flow collection. Enabling compression reduces the network bandwidth required to transport flows and decreases the storage footprint on Kafka brokers.
25+
+
26+
The following key benefits include:
27+
+
28+
* Reduced network load: Compressing flow data minimizes the traffic volume between the eBPF agent or flowlogs-pipeline and your Kafka cluster.
29+
* Storage efficiency: Smaller message sizes lead to improved disk space utilization on Kafka brokers.
30+
* Tunable performance: Choose from several compression algorithms, such as `gzip`, `snappy`, `lz4`, or `zstd`, to balance CPU usage with compression ratios.
31+
+
32+
To enable this feature, configure the `spec.kafka.compression` and `spec.exporters.kafka.compression` fields in the `FlowCollector` custom resource.
33+
34+
Simplified secondary network indexing::
35+
The configuration process for secondary network indexing is now simplified.
36+
+
37+
The `name` field in the `spec.processor.advanced.secondaryNetworks` list is deprecated and ignored. The Network Observability Operator automatically evaluates all secondary networks regardless of their assigned names, removing the requirement for manual name-matching entries in the `FlowCollector` CR.
38+
39+
{product-title} web console compatibility::
40+
The Network Observability web console plugin is updated to support {product-title} 4.22 and later. Backward compatibility is maintained for {product-title} versions 4.14 through 4.21.

‎modules/network-observability-operator-release-notes-1-12-technology-preview.adoc‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
// Module included in the following assemblies:
2+
// * network_observability/network-observability-release-notes.adoc
3+
4+
:_mod-docs-content-type: REFERENCE
5+
[id="network-observability-operator-release-notes-1-12-technology-preview_{context}"]
6+
= Network Observability Operator 1.12 Technology Preview features
7+
8+
[role="_abstract"]
9+
The Network Observability Operator is included by default as a Technology Preview feature in 1.12 and {product-title} 4.22. You can explore network traffic visualization and monitoring capabilities without performing a separate installation.
10+
11+
To use this Technology Preview feature, you must enable the `NetworkObservabilityInstall` feature gate through a manifest file during cluster installation.

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

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -8,22 +8,18 @@ include::_attributes/common-attributes.adoc[]
88
toc::[]
99

1010
[role="_abstract"]
11-
Find information about new features, security advisories, fixed issues, and known issues for the Network Observability Operator, and stay informed about changes and performance enhancements in the latest version of the operator for {product-title}.
11+
Review new features, enhancements, fixed issues, and known issues for the Network Observability Operator. These release notes provide information to help you understand changes and security advisories in the latest Operator release.
1212

1313
The Network Observability Operator enables administrators to observe and analyze network traffic flows for {product-title} clusters.
1414

1515
These release notes track the development of the Network Observability Operator in the {product-title}.
1616

17-
include::modules/network-observability-operator-release-notes-1-11-2-advisory.adoc[leveloffset=+1]
17+
include::modules/network-observability-operator-release-notes-1-12-advisory.adoc[leveloffset=+1]
1818

19-
include::modules/network-observability-operator-release-notes-1-11-1-advisory.adoc[leveloffset=+1]
19+
include::modules/network-observability-operator-release-notes-1-12-new-features-enhancements.adoc[leveloffset=+1]
2020

21-
include::modules/network-observability-operator-release-notes-1-11-1-fixed-issues.adoc[leveloffset=+1]
21+
include::modules/network-observability-operator-release-notes-1-12-technology-preview.adoc[leveloffset=+1]
2222

23-
include::modules/network-observability-operator-release-notes-1-11-advisory.adoc[leveloffset=+1]
23+
include::modules/network-observability-operator-release-notes-1-12-fixed-issues.adoc[leveloffset=+1]
2424

25-
include::modules/network-observability-operator-release-notes-1-11-new-features-enhancements.adoc[leveloffset=+1]
26-
27-
include::modules/network-observability-operator-release-notes-1-11-known-issues.adoc[leveloffset=+1]
28-
29-
include::modules/network-observability-operator-release-notes-1-11-fixed-issues.adoc[leveloffset=+1]
25+
include::modules/network-observability-operator-release-notes-1-12-known-issues.adoc[leveloffset=+1]

‎observability/network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,21 @@ These release notes track past developments of the Network Observability Operato
1313

1414
The Network Observability Operator enables administrators to observe and analyze network traffic flows for {product-title} clusters.
1515

16+
17+
include::modules/network-observability-operator-release-notes-1-11-2-advisory.adoc[leveloffset=+1]
18+
19+
include::modules/network-observability-operator-release-notes-1-11-1-advisory.adoc[leveloffset=+1]
20+
21+
include::modules/network-observability-operator-release-notes-1-11-1-fixed-issues.adoc[leveloffset=+1]
22+
23+
include::modules/network-observability-operator-release-notes-1-11-advisory.adoc[leveloffset=+1]
24+
25+
include::modules/network-observability-operator-release-notes-1-11-new-features-enhancements.adoc[leveloffset=+1]
26+
27+
include::modules/network-observability-operator-release-notes-1-11-known-issues.adoc[leveloffset=+1]
28+
29+
include::modules/network-observability-operator-release-notes-1-11-fixed-issues.adoc[leveloffset=+1]
30+
1631
include::modules/network-observability-operator-release-notes-1-10-1.adoc[leveloffset=+1]
1732

1833
include::modules/network-observability-operator-release-notes-1-10-1-cves.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)