You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before this update, users could create a `FlowMetric` custom resource (`CR`) with an invalid metric name. Although the `FlowMetric` `CR` was successfully created, the underlying metric would fail silently without providing any error feedback to the user.
14
+
Before this update, users could create a `FlowMetric` custom resource (CR) with an invalid metric name. Although the `FlowMetric` CR was successfully created, the underlying metric would fail silently without providing any error feedback to the user.
15
15
16
-
With this release, the `FlowMetric` `metricName` and `remap` fields are now validated before creation, so users are immediately notified if they enter an invalid name.
16
+
With this release, the `FlowMetric`, `metricName`, and `remap` fields are now validated before creation, so users are immediately notified if they enter an invalid name.
Before this update, performance issues in the underlying library caused the `HTML-to-image` export function to take a long time, leading to browser freezing.
23
+
Before this update, performance issues in the underlying library caused the `html-to-image` export function to take a long time, leading to browser freezing.
24
24
25
25
With this release, the performance of the `html-to-image` library has been improved, reducing export wait times and eliminating browser freezing during image generation.
Before this update, when users selected `eBPF` features that require `privileged mode`, the features would often fail without clearly informing the user that `privileged mode` was missing or needed to be enabled.
32
+
Before this update, when users selected `eBPF` features that require `privileged` mode, the features would often fail without clearly informing the user that `privileged mode` was missing or needed to be enabled.
33
33
34
34
With this release, a validation hook immediately warns the user if the configuration is inconsistent. This improves user understanding and prevents misconfiguration.
== Reduced default tolerations for network observability components
49
49
Before this update, a default toleration was set on all network observability components to allow them to be scheduled on any node, including those tainted with `NoSchedule`. This could potentially block cluster upgrades.
50
50
51
-
With this release, the default toleration is now only maintained for the eBPF agents and the `Flowlogs-Pipeline` when configured in `Direct` mode. The toleration has been removed from the {product-title} web console plugin and the `Flowlogs-Pipeline` when configured in `Kafka` mode.
51
+
With this release, the default toleration is now only maintained for the `eBPF` agents and the `Flowlogs-Pipeline` when configured in `Direct` mode. The toleration has been removed from the {product-title} web console plugin and the `Flowlogs-Pipeline` when configured in `Kafka` mode.
52
52
53
53
Additionally, while tolerations were always configurable in the `FlowCollector` custom resource (CR), it was previously impossible to replace the tolerations with an empty list. It is now possible to replace the tolerations with an empty list.
== eBPF agent compatibility with older {product-title} versions
13
-
The eBPF agent used in the Network Observability Command Line Interface (CLI) packet capture feature is incompatible with {product-title} (OCP) versions 4.16 and older.
13
+
The eBPF agent used in the Network Observability Command Line Interface (CLI) packet capture feature is incompatible with {product-title} versions 4.16 and older.
14
14
15
15
This limitation prevents the eBPF-based Packet Capture Agent (PCA) from functioning correctly on those older clusters.
Copy file name to clipboardExpand all lines: modules/network-observability-operator-release-notes-1-10-new-features-enhancements.adoc
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
= Network Observability Operator 1.10 new features and enhancements
7
7
8
8
[role="_abstract"]
9
-
The Network Observability Operator 1.10 release enhances security, improves performance, and introduces new CLI/UI tools for better network flow management.
9
+
The Network Observability Operator 1.10 release enhances security, improves performance, and introduces new CLIUI tools for better network flow management.
10
10
11
11
[id="network-policy-updates_{context}"]
12
12
== Network policy updates
@@ -21,22 +21,22 @@ This release brings the following new features and updates to the Network Observ
21
21
22
22
*Table view enhancements*
23
23
24
-
* Customizable columns: The `Manage Columns` button lets you select which columns to display and tailor the table to your needs.
24
+
* Customizable columns: Click *Manage Columns* to select which columns to display, and tailor the table to your needs.
25
25
* Smart filtering: Live filters now include auto-suggestions, making it easier to select the right keys and values.
26
26
* Packet preview: When capturing packets, click a row to inspect the `pcap` content directly.
27
27
28
28
*Terminal-based line charts enhancements*
29
29
30
30
* Metrics visualization: Real-time graphs are rendered directly in the CLI.
31
-
* Panel selection: Choose from predefined views or customize view using the `Manage Panels` popup to selectively view charts of specific metrics.
31
+
* Panel selection: Choose from predefined views or customize views by using the *Manage Panels* pop-up menu to selectively view charts of specific metrics.
There is a new view in the network observability console plugin to configure the `FlowCollector` custom resource (CR). This new view:
35
+
The network observability console plugin includes a new view to configure the `FlowCollector` custom resource (CR). From this view, you can complete the following tasks:
36
36
37
-
* Makes it easier to configure the `FlowCollector` CR.
38
-
* Introduces a resource footprint calculator.
39
-
* Increases the visibility of issues such as configuration warnings or high metrics cardinality.
37
+
* Configure the `FlowCollector` CR.
38
+
* Calculate your resource footprint.
39
+
* Gain increased of issues such as configuration warnings or high metrics cardinality.
This release introduces new alert functionality, and custom alert configuration. These capabilities are Technology Preview features, and must be explicitly enabled.
11
11
12
-
The new alerts appear in *Observe* → *Alerting* → *Alerting rules* tab in the {product-title} web console.
12
+
TTo view the new alerts, in the {product-title} web console, click *Observe* → *Alerting* → *Alerting rules*.
== Network Observability Operator Network Health dashboard (Technology Preview)
16
-
When you enable the Technology Preview alerts functionality in the Network Observability Operator, a new *Network Health* dashboard appears in {product-title} web console → *Observe*.
16
+
When you enable the Technology Preview alerts functionality in the Network Observability Operator, you can view a a new *Network Health* dashboard in the {product-title} web console by clicking *Observe*.
17
17
18
18
The *Network Health* dashboard provides a summary of triggered alerts, distinguishing between critical, warning, and minor issues, and also shows pending alerts.
0 commit comments