From a8ddaebd216ba8d011def6d18ef7f4f9a8bfaa41 Mon Sep 17 00:00:00 2001 From: Gwynne Monahan Date: Thu, 13 Nov 2025 10:05:09 -0600 Subject: [PATCH] OSDOCS-15828 [NETOBSERV] Refactor release notes 1.7 --- ...ator-release-notes-1-7-0-fixed-issues.adoc | 23 ++ ...ator-release-notes-1-7-0-known-issues.adoc | 33 ++ ...s-1-7-0-new-features-and-enhancements.adoc | 57 +++ ...vability-operator-release-notes-1-7-0.adoc | 11 + ...-observability-operator-release-notes.adoc | 326 ------------------ ...bility-operator-release-notes-archive.adoc | 9 +- 6 files changed, 132 insertions(+), 327 deletions(-) create mode 100644 modules/network-observability-operator-release-notes-1-7-0-fixed-issues.adoc create mode 100644 modules/network-observability-operator-release-notes-1-7-0-known-issues.adoc create mode 100644 modules/network-observability-operator-release-notes-1-7-0-new-features-and-enhancements.adoc create mode 100644 modules/network-observability-operator-release-notes-1-7-0.adoc diff --git a/modules/network-observability-operator-release-notes-1-7-0-fixed-issues.adoc b/modules/network-observability-operator-release-notes-1-7-0-fixed-issues.adoc new file mode 100644 index 000000000000..3016ed366b7c --- /dev/null +++ b/modules/network-observability-operator-release-notes-1-7-0-fixed-issues.adoc @@ -0,0 +1,23 @@ +// Module included in the following assemblies: +// * network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc + +:_mod-docs-content-type: REFERENCE +[id="network-observability-operator-release-notes-1-7-0-fixed-issues_{context}"] += Network Observability Operator 1.7.0 fixed issues + +[role="_abstract"] +You can review the following fixed issues for the Network Observability Operator 1.7.0 release. + +* Previously, when using a {op-system-base} 9.2 real-time kernel, some of the webhooks did not work. Now, a fix is in place to check whether this {op-system-base} 9.2 real-time kernel is being used. If the kernel is being used, a warning is displayed about the features that do not work, such as packet drop and neither Round-trip Time when using `s390x` architecture. The fix is in OpenShift 4.16 and later. (link:https://issues.redhat.com/browse/NETOBSERV-1808[*NETOBSERV-1808*]) +* Previously, in the *Manage panels* dialog in the *Overview* tab, filtering on *total*, *bar*, *donut*, or *line* did not show a result. Now the available panels are correctly filtered. (link:https://issues.redhat.com/browse/NETOBSERV-1540[*NETOBSERV-1540*]) +* Previously, under high stress, the eBPF agents were susceptible to enter into a state where they generated a high number of small flows, almost not aggregated. With this fix, the aggregation process is still maintained under high stress, resulting in less flows being created. This fix improves the resource consumption not only in the eBPF agent but also in `flowlogs-pipeline` and Loki. (link:https://issues.redhat.com/browse/NETOBSERV-1564[*NETOBSERV-1564*]) +* Previously, when the `workload_flows_total` metric was enabled instead of the `namespace_flows_total` metric, the health dashboard stopped showing `By namespace` flow charts. With this fix, the health dashboard now shows the flow charts when the `workload_flows_total` is enabled. (link:https://issues.redhat.com/browse/NETOBSERV-1746[*NETOBSERV-1746*]) +* Previously, when you used the `FlowMetrics` API to generate a custom metric and later modified its labels, such as by adding a new label, the metric stopped populating and an error was shown in the `flowlogs-pipeline` logs. With this fix, you can modify the labels, and the error is no longer raised in the `flowlogs-pipeline` logs. (link:https://issues.redhat.com/browse/NETOBSERV-1748[*NETOBSERV-1748*]) +* Previously, there was an inconsistency with the default Loki `WriteBatchSize` configuration: it was set to 100 KB in the `FlowCollector` CRD default, and 10 MB in the OLM sample or default configuration. Both are now aligned to 10 MB, which generally provides better performances and less resource footprint. (link:https://issues.redhat.com/browse/NETOBSERV-1766[*NETOBSERV-1766*]) +* Previously, the eBPF flow filter on ports was ignored if you did not specify a protocol. With this fix, you can set eBPF flow filters independently on ports and or protocols. (link:https://issues.redhat.com/browse/NETOBSERV-1779[*NETOBSERV-1779*]) +* Previously, traffic from Pods to Services was hidden from the *Topology view*. Only the return traffic from Services to Pods was visible. With this fix, that traffic is correctly displayed. (link:https://issues.redhat.com/browse/NETOBSERV-1788[*NETOBSERV-1788*]) +* Previously, non-cluster administrator users that had access to Network Observability saw an error in the console plugin when they tried to filter for something that triggered auto-completion, such as a namespace. With this fix, no error is displayed, and the auto-completion returns the expected results. (link:https://issues.redhat.com/browse/NETOBSERV-1798[*NETOBSERV-1798*]) +* When the secondary interface support was added, you had to iterate multiple times to register the per network namespace with the netlink to learn about interface notifications. At the same time, unsuccessful handlers caused a leaking file descriptor because with TCX hook, unlike TC, handlers needed to be explicitly removed when the interface went down. Furthermore, when the network namespace was deleted, there was no Go close channel event to terminate the netlink goroutine socket, which caused go threads to leak. Now, there are no longer leaking file descriptors or go threads when you create or delete pods. (link:https://issues.redhat.com/browse/NETOBSERV-1805[*NETOBSERV-1805*]) +* Previously, the ICMP type and value were displaying 'n/a' in the *Traffic flows* table even when related data was available in the flow JSON. With this fix, ICMP columns display related values as expected in the flow table. (link:https://issues.redhat.com/browse/NETOBSERV-1806[*NETOBSERV-1806*]) +* Previously in the console plugin, it wasn't always possible to filter for unset fields, such as unset DNS latency. With this fix, filtering on unset fields is now possible. (link:https://issues.redhat.com/browse/NETOBSERV-1816[*NETOBSERV-1816*]) +* Previously, when you cleared filters in the OpenShift web console plugin, sometimes the filters reappeared after you navigated to another page and returned to the page with filters. With this fix, filters do not unexpectedly reappear after they are cleared. (link:https://issues.redhat.com/browse/NETOBSERV-1733[*NETOBSERV-1733*]) diff --git a/modules/network-observability-operator-release-notes-1-7-0-known-issues.adoc b/modules/network-observability-operator-release-notes-1-7-0-known-issues.adoc new file mode 100644 index 000000000000..c01fe3de5f4d --- /dev/null +++ b/modules/network-observability-operator-release-notes-1-7-0-known-issues.adoc @@ -0,0 +1,33 @@ +// Module included in the following assemblies: +// * network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc + +:_mod-docs-content-type: REFERENCE +[id="network-observability-operator-release-notes-1-7-0-known-issues_{context}"] += Network Observability Operator 1.7.0 known issues + +[role="_abstract"] +You can review the following known issues for the Network Observability Operator 1.7.0 release. + +* When you use the must-gather tool with network observability, logs are not collected when the cluster has FIPS enabled. (link:https://issues.redhat.com/browse/NETOBSERV-1830[*NETOBSERV-1830*]) +* When the `spec.networkPolicy` is enabled in the `FlowCollector`, which installs a network policy on the `netobserv` namespace, it is impossible to use the `FlowMetrics` API. The network policy blocks calls to the validation webhook. As a workaround, use the following network policy: ++ +[source,yaml] +---- +kind: NetworkPolicy +apiVersion: networking.k8s.io/v1 +metadata: + name: allow-from-hostnetwork + namespace: netobserv +spec: + podSelector: + matchLabels: + app: netobserv-operator + ingress: + - from: + - namespaceSelector: + matchLabels: + policy-group.network.openshift.io/host-network: '' + policyTypes: + - Ingress +---- +(link:https://issues.redhat.com/browse/NETOBSERV-1934[*NETOBSERV-193*]) diff --git a/modules/network-observability-operator-release-notes-1-7-0-new-features-and-enhancements.adoc b/modules/network-observability-operator-release-notes-1-7-0-new-features-and-enhancements.adoc new file mode 100644 index 000000000000..b2e8fd95891b --- /dev/null +++ b/modules/network-observability-operator-release-notes-1-7-0-new-features-and-enhancements.adoc @@ -0,0 +1,57 @@ +// Module included in the following assemblies: +// * network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc + +:_mod-docs-content-type: REFERENCE +[id="network-observability-operator-release-notes-1-7-0-new-features-and-enhancements_{context}"] += Network Observability Operator 1.7.0 new features and enhancements + +[role="_abstract"] +You can review the following new features and enhancements for the Network Observability Operator 1.7.0 release. + +[id="network-observability-operator-otel-1-7_{context}"] +== OpenTelemetry support +You can now export enriched network flows to a compatible OpenTelemetry endpoint, such as the Red{nbsp}Hat build of OpenTelemetry. For more information see xref:../../../observability/network_observability/configuring-operator.adoc#network-observability-enriched-flows_network_observability[Export enriched network flow data]. + +[id="network-observability-operator-developer-perspective-1-7_{context}"] +== Network observability Developer perspective +You can now use network observability in the *Developer* perspective. For more information, see xref:../../../observability/network_observability/network-observability-overview.adoc#network-observability-openshift-console-integration_network-observability-overview[{product-title} console integration]. + +[id="tcp-flags-filters-1-7_{context}"] +== TCP flags filtering +You can now use the `tcpFlags` filter to limit the volume of packets processed by the eBPF program. For more information, see xref:../../../observability/network_observability/observing-network-traffic.adoc#network-observability-flowcollector-flowfilter-parameters_nw-observe-network-traffic[Flow filter configuration parameters], xref:../../../observability/network_observability/observing-network-traffic.adoc#network-observability-ebpf-flow-rule-filter_nw-observe-network-traffic[eBPF flow rule filter], and xref:../../../observability/network_observability/metrics-alerts-dashboards.adoc#network-observability-tcp-flag-syn-flood_metrics-dashboards-alerts[Detecting SYN flooding using the FlowMetric API and TCP flags]. + +[id="network-observability-virtualization_{context}"] +== Network observability for OpenShift Virtualization +You can observe networking patterns on an {VirtProductName} setup by identifying eBPF-enriched network flows coming from VMs that are connected to secondary networks, such as through Open Virtual Network (OVN)-Kubernetes. For more information, see xref:../../../observability/network_observability/network-observability-secondary-networks.adoc#network-observability-virtualization-config_network-observability-secondary-networks[Configuring virtual machine (VM) secondary network interfaces for network observability]. + +[id="network-observability-network-policy-1-7_{context}"] +== Network policy deploys in the FlowCollector custom resource (CR) +With this release, you can configure the `FlowCollector` custom resource (CR) to deploy a network policy for network observability. Previously, if you wanted a network policy, you had to manually create one. The option to manually create a network policy is still available. For more information, see xref:../../../observability/network_observability/network-observability-network-policy.adoc#network-observability-deploy-network-policy_network_observability[Configuring an ingress network policy by using the FlowCollector custom resource]. + +[id="network-observability-fips-compliance-1-7_{context}"] +== FIPS compliance +* You can install and use the Network Observability Operator in an {product-title} cluster running in FIPS mode. ++ +-- +include::snippets/fips-snippet.adoc[] +-- + +[id="network-observability-dns-enhancements-1-7_{context}"] +== eBPF agent enhancements +The following enhancements are available for the eBPF agent: + +* If the DNS service maps to a different port than `53`, you can specify this DNS tracking port using `spec.agent.ebpf.advanced.env.DNS_TRACKING_PORT`. +* You can now use two ports for transport protocols (TCP, UDP, or SCTP) filtering rules. +* You can now filter on transport ports with a wildcard protocol by leaving the protocol field empty. + +For more information, see xref:../../../observability/network_observability/flowcollector-api.adoc#spec-agent-ebpf-advanced[FlowCollector API specifications]. + +[id="network-observability-cli-1-7_{context}"] +== Network Observability CLI +The Network Observability CLI (`oc netobserv`), is now generally available. The following enhancements have been made since the 1.6 Technology Preview release: + +* There are now eBPF enrichment filters for packet capture similar to flow capture. +* You can now use filter `tcp_flags` with both flow and packets capture. +* The auto-teardown option is available when max-bytes or max-time is reached. + +For more information, see xref:../../../observability/network_observability/netobserv_cli/netobserv-cli-install.adoc#network-observability-netoberv-cli-about_netobserv-cli-install[About the Network Observability CLI] and link:https://access.redhat.com/errata/RHEA-2024:8264[Network Observability CLI 1.7.0]. diff --git a/modules/network-observability-operator-release-notes-1-7-0.adoc b/modules/network-observability-operator-release-notes-1-7-0.adoc new file mode 100644 index 000000000000..be42b8ae9e73 --- /dev/null +++ b/modules/network-observability-operator-release-notes-1-7-0.adoc @@ -0,0 +1,11 @@ +// Module included in the following assemblies: +// * network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc + +:_mod-docs-content-type: REFERENCE +[id="network-observability-operator-release-notes-1-7-0_{context}"] += Network Observability Operator 1.7.0 advisory + +[role="_abstract"] +You can review the advisory for the Network Observability Operator 1.7.0 release. + +* link:https://access.redhat.com/errata/RHSA-2024:8014[Network Observability Operator 1.7.0] \ No newline at end of file diff --git a/observability/network_observability/network-observability-operator-release-notes.adoc b/observability/network_observability/network-observability-operator-release-notes.adoc index a2920a5bb5cb..10a0c0519a66 100644 --- a/observability/network_observability/network-observability-operator-release-notes.adoc +++ b/observability/network_observability/network-observability-operator-release-notes.adoc @@ -238,329 +238,3 @@ For more information, see xref:../../observability/network_observability/netobse * 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*]) - -[id="network-observability-operator-release-notes-1-7_{context}"] -== Network Observability Operator 1.7.0 -The following advisory is available for the Network Observability Operator 1.7.0: - -* link:https://access.redhat.com/errata/RHSA-2024:8014[Network Observability Operator 1.7.0] - -[id="network-observability-operator-1.7.0-features-enhancements_{context}"] -=== New features and enhancements - -[id="network-observability-operator-otel-1-7_{context}"] -==== OpenTelemetry support -You can now export enriched network flows to a compatible OpenTelemetry endpoint, such as the Red{nbsp}Hat build of OpenTelemetry. For more information see xref:../../observability/network_observability/configuring-operator.adoc#network-observability-enriched-flows_network_observability[Export enriched network flow data]. - -[id="network-observability-operator-developer-perspective-1-7_{context}"] -==== Network observability Developer perspective -You can now use network observability in the *Developer* perspective. For more information, see xref:../../observability/network_observability/network-observability-overview.adoc#network-observability-openshift-console-integration_network-observability-overview[{product-title} console integration]. - -==== TCP flags filtering -You can now use the `tcpFlags` filter to limit the volume of packets processed by the eBPF program. For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-flowcollector-flowfilter-parameters_nw-observe-network-traffic[Flow filter configuration parameters], xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-ebpf-flow-rule-filter_nw-observe-network-traffic[eBPF flow rule filter], and xref:../../observability/network_observability/metrics-alerts-dashboards.adoc#network-observability-tcp-flag-syn-flood_metrics-dashboards-alerts[Detecting SYN flooding using the FlowMetric API and TCP flags]. - -[id="network-observability-virtualization_{context}"] -==== Network observability for OpenShift Virtualization -You can observe networking patterns on an {VirtProductName} setup by identifying eBPF-enriched network flows coming from VMs that are connected to secondary networks, such as through Open Virtual Network (OVN)-Kubernetes. For more information, see xref:../../observability/network_observability/network-observability-secondary-networks.adoc#network-observability-virtualization-config_network-observability-secondary-networks[Configuring virtual machine (VM) secondary network interfaces for network observability]. - -[id="network-observability-network-policy-1-7_{context}"] -==== Network policy deploys in the FlowCollector custom resource (CR) -With this release, you can configure the `FlowCollector` CR to deploy a network policy for network observability. Previously, if you wanted a network policy, you had to manually create one. The option to manually create a network policy is still available. For more information, see xref:../../observability/network_observability/network-observability-network-policy.adoc#network-observability-deploy-network-policy_network_observability[Configuring an ingress network policy by using the FlowCollector custom resource]. - -[id="network-observability-fips-compliance-1-7_{context}"] -==== FIPS compliance -* You can install and use the Network Observability Operator in an {product-title} cluster running in FIPS mode. -+ --- -include::snippets/fips-snippet.adoc[] --- - -[id="network-observability-dns-enhancements-1-7_{context}"] -==== eBPF agent enhancements -The following enhancements are available for the eBPF agent: - -* If the DNS service maps to a different port than `53`, you can specify this DNS tracking port using `spec.agent.ebpf.advanced.env.DNS_TRACKING_PORT`. -* You can now use two ports for transport protocols (TCP, UDP, or SCTP) filtering rules. -* You can now filter on transport ports with a wildcard protocol by leaving the protocol field empty. - -For more information, see xref:../../observability/network_observability/flowcollector-api.adoc#spec-agent-ebpf-advanced[FlowCollector API specifications]. - -[id="network-observability-cli-1-7_{context}"] -==== Network Observability CLI -The Network Observability CLI (`oc netobserv`), is now generally available. The following enhancements have been made since the 1.6 Technology Preview release: -* There are now eBPF enrichment filters for packet capture similar to flow capture. -* You can now use filter `tcp_flags` with both flow and packets capture. -* The auto-teardown option is available when max-bytes or max-time is reached. -For more information, see xref:../../observability/network_observability/netobserv_cli/netobserv-cli-install.adoc#network-observability-netoberv-cli-about_netobserv-cli-install[Network Observability CLI] and link:https://access.redhat.com/errata/RHEA-2024:8264[Network Observability CLI 1.7.0]. - -[id="network-observability-operator-1-7-bug-fixes_{context}"] -=== Bug fixes - -* Previously, when using a {op-system-base} 9.2 real-time kernel, some of the webhooks did not work. Now, a fix is in place to check whether this {op-system-base} 9.2 real-time kernel is being used. If the kernel is being used, a warning is displayed about the features that do not work, such as packet drop and neither Round-trip Time when using `s390x` architecture. The fix is in OpenShift 4.16 and later. (link:https://issues.redhat.com/browse/NETOBSERV-1808[*NETOBSERV-1808*]) -* Previously, in the *Manage panels* dialog in the *Overview* tab, filtering on *total*, *bar*, *donut*, or *line* did not show a result. Now the available panels are correctly filtered. (link:https://issues.redhat.com/browse/NETOBSERV-1540[*NETOBSERV-1540*]) -* Previously, under high stress, the eBPF agents were susceptible to enter into a state where they generated a high number of small flows, almost not aggregated. With this fix, the aggregation process is still maintained under high stress, resulting in less flows being created. This fix improves the resource consumption not only in the eBPF agent but also in `flowlogs-pipeline` and Loki. (link:https://issues.redhat.com/browse/NETOBSERV-1564[*NETOBSERV-1564*]) -* Previously, when the `workload_flows_total` metric was enabled instead of the `namespace_flows_total` metric, the health dashboard stopped showing `By namespace` flow charts. With this fix, the health dashboard now shows the flow charts when the `workload_flows_total` is enabled. (link:https://issues.redhat.com/browse/NETOBSERV-1746[*NETOBSERV-1746*]) -* Previously, when you used the `FlowMetrics` API to generate a custom metric and later modified its labels, such as by adding a new label, the metric stopped populating and an error was shown in the `flowlogs-pipeline` logs. With this fix, you can modify the labels, and the error is no longer raised in the `flowlogs-pipeline` logs. (link:https://issues.redhat.com/browse/NETOBSERV-1748[*NETOBSERV-1748*]) -* Previously, there was an inconsistency with the default Loki `WriteBatchSize` configuration: it was set to 100 KB in the `FlowCollector` CRD default, and 10 MB in the OLM sample or default configuration. Both are now aligned to 10 MB, which generally provides better performances and less resource footprint. (link:https://issues.redhat.com/browse/NETOBSERV-1766[*NETOBSERV-1766*]) -* Previously, the eBPF flow filter on ports was ignored if you did not specify a protocol. With this fix, you can set eBPF flow filters independently on ports and or protocols. (link:https://issues.redhat.com/browse/NETOBSERV-1779[*NETOBSERV-1779*]) -* Previously, traffic from Pods to Services was hidden from the *Topology view*. Only the return traffic from Services to Pods was visible. With this fix, that traffic is correctly displayed. (link:https://issues.redhat.com/browse/NETOBSERV-1788[*NETOBSERV-1788*]) -* Previously, non-cluster administrator users that had access to Network Observability saw an error in the console plugin when they tried to filter for something that triggered auto-completion, such as a namespace. With this fix, no error is displayed, and the auto-completion returns the expected results. (link:https://issues.redhat.com/browse/NETOBSERV-1798[*NETOBSERV-1798*]) -* When the secondary interface support was added, you had to iterate multiple times to register the per network namespace with the netlink to learn about interface notifications. At the same time, unsuccessful handlers caused a leaking file descriptor because with TCX hook, unlike TC, handlers needed to be explicitly removed when the interface went down. Furthermore, when the network namespace was deleted, there was no Go close channel event to terminate the netlink goroutine socket, which caused go threads to leak. Now, there are no longer leaking file descriptors or go threads when you create or delete pods. (link:https://issues.redhat.com/browse/NETOBSERV-1805[*NETOBSERV-1805*]) -* Previously, the ICMP type and value were displaying 'n/a' in the *Traffic flows* table even when related data was available in the flow JSON. With this fix, ICMP columns display related values as expected in the flow table. (link:https://issues.redhat.com/browse/NETOBSERV-1806[*NETOBSERV-1806*]) -* Previously in the console plugin, it wasn't always possible to filter for unset fields, such as unset DNS latency. With this fix, filtering on unset fields is now possible. (link:https://issues.redhat.com/browse/NETOBSERV-1816[*NETOBSERV-1816*]) -* Previously, when you cleared filters in the OpenShift web console plugin, sometimes the filters reappeared after you navigated to another page and returned to the page with filters. With this fix, filters do not unexpectedly reappear after they are cleared. (link:https://issues.redhat.com/browse/NETOBSERV-1733[*NETOBSERV-1733*]) - -[id="network-observability-operator-1-7-known-issues_{context}"] -=== Known issues -* WWhen you use the must-gather tool with network observability, logs are not collected when the cluster has FIPS enabled. (link:https://issues.redhat.com/browse/NETOBSERV-1830[*NETOBSERV-1830*]) -* When the `spec.networkPolicy` is enabled in the `FlowCollector`, which installs a network policy on the `netobserv` namespace, it is impossible to use the `FlowMetrics` API. The network policy blocks calls to the validation webhook. As a workaround, use the following network policy: -+ -[source,yaml] ----- -kind: NetworkPolicy -apiVersion: networking.k8s.io/v1 -metadata: - name: allow-from-hostnetwork - namespace: netobserv -spec: - podSelector: - matchLabels: - app: netobserv-operator - ingress: - - from: - - namespaceSelector: - matchLabels: - policy-group.network.openshift.io/host-network: '' - policyTypes: - - Ingress ----- -(link:https://issues.redhat.com/browse/NETOBSERV-1934[*NETOBSERV-193*]) - -[id="network-observability-operator-release-notes-1-6-2_{context}"] -== Network Observability Operator 1.6.2 -The following advisory is available for the Network Observability Operator 1.6.2: - -* link:https://access.redhat.com/errata/RHSA-2024:7074[2024:7074 Network Observability Operator 1.6.2] - -[id="network-observability-operator-CVE-1-6-2_{context}"] -=== CVEs -* link:https://access.redhat.com/security/cve/CVE-2024-24791[CVE-2024-24791] - -[id="network-observability-operator-1-6-2-bug-fixes_{context}"] -=== Bug fixes -* When the secondary interface support was added, there was a need to iterate multiple times to register the per network namespace with the netlink to learn about interface notifications. At the same time, unsuccessful handlers caused a leaking file descriptor because with TCX hook, unlike TC, handlers needed to be explicitly removed when the interface went down. Now, there is no longer leaking file descriptors when creating and deleting pods. (link:https://issues.redhat.com/browse/NETOBSERV-1805[*NETOBSERV-1805*]) - -=== Known issues -There was a compatibility issue with console plugins that would have prevented network observability from being installed on future versions of an {product-title} cluster. By upgrading to 1.6.2, the compatibility issue is resolved and network observability can be installed as expected. (link:https://issues.redhat.com/browse/NETOBSERV-1737[*NETOBSERV-1737*]) - -[id="network-observability-operator-release-notes-1-6-1_{context}"] -== Network Observability Operator 1.6.1 -The following advisory is available for the Network Observability Operator 1.6.1: - -* link:https://access.redhat.com/errata/RHSA-2024:4785[2024:4785 Network Observability Operator 1.6.1] - -[id="network-observability-operator-CVE-1-6-1_{context}"] -=== CVEs -* link:https://access.redhat.com/errata/RHSA-2024:4237[RHSA-2024:4237] -* link:https://access.redhat.com/errata/RHSA-2024:4212[RHSA-2024:4212] - -[id="network-observability-operator-1.6.1-bug-fixes_{context}"] -=== Bug fixes -* Previously, information about packet drops, such as the cause and TCP state, was only available in the Loki datastore and not in Prometheus. For that reason, the drop statistics in the OpenShift web console plugin *Overview* was only available with Loki. With this fix, information about packet drops is also added to metrics, so you can view drops statistics when Loki is disabled. (link:https://issues.redhat.com/browse/NETOBSERV-1649[*NETOBSERV-1649*]) -* When the eBPF agent `PacketDrop` feature was enabled, and sampling was configured to a value greater than `1`, reported dropped bytes and dropped packets ignored the sampling configuration. While this was done on purpose, so as not to miss any drops, a side effect was that the reported proportion of drops compared with non-drops became biased. For example, at a very high sampling rate, such as `1:1000`, it was likely that almost all the traffic appears to be dropped when observed from the console plugin. With this fix, the sampling configuration is honored with dropped bytes and packets. (link:https://issues.redhat.com/browse/NETOBSERV-1676[*NETOBSERV-1676*]) -* Previously, the SR-IOV secondary interface was not detected if the interface was created first and then the eBPF agent was deployed. It was only detected if the agent was deployed first and then the SR-IOV interface was created. With this fix, the SR-IOV secondary interface is detected no matter the sequence of the deployments. (link:https://issues.redhat.com/browse/NETOBSERV-1697[*NETOBSERV-1697*]) -* Previously, when Loki was disabled, the *Topology* view in the OpenShift web console displayed the *Cluster* and *Zone* aggregation options in the slider beside the network topology diagram, even when the related features were not enabled. With this fix, the slider now only displays options according to the enabled features. (link:https://issues.redhat.com/browse/NETOBSERV-1705[*NETOBSERV-1705*]) -* Previously, when Loki was disabled, and the OpenShift web console was first loading, an error would occur: `Request failed with status code 400 Loki is disabled`. With this fix, the errors no longer occur. (link:https://issues.redhat.com/browse/NETOBSERV-1706[*NETOBSERV-1706*]) -* Previously, in the *Topology* view of the OpenShift web console, when clicking on the *Step into* icon next to any graph node, the filters were not applied as required in order to set the focus to the selected graph node, resulting in showing a wide view of the *Topology* view in the OpenShift web console. With this fix, the filters are correctly set, effectively narrowing down the *Topology*. As part of this change, clicking the *Step into* icon on a *Node* now brings you to the *Resource* scope instead of the *Namespaces* scope. (link:https://issues.redhat.com/browse/NETOBSERV-1720[*NETOBSERV-1720*]) -* Previously, when Loki was disabled, in the *Topology* view of the OpenShift web console with the *Scope* set to *Owner*, clicking on the *Step into* icon next to any graph node would bring the *Scope* to *Resource*, which is not available without Loki, so an error message was shown. With this fix, the *Step into* icon is hidden in the *Owner* scope when Loki is disabled, so this scenario no longer occurs.(link:https://issues.redhat.com/browse/NETOBSERV-1721[*NETOBSERV-1721*]) -* Previously, when Loki was disabled, an error was displayed in the *Topology* view of the OpenShift web console when a group was set, but then the scope was changed so that the group becomes invalid. With this fix, the invalid group is removed, preventing the error. (link:https://issues.redhat.com/browse/NETOBSERV-1722[*NETOBSERV-1722*]) -* When creating a `FlowCollector` resource from the OpenShift web console *Form view*, as opposed to the *YAML view*, the following settings were incorrectly managed by the web console: `agent.ebpf.metrics.enable` and `processor.subnetLabels.openShiftAutoDetect`. These settings can only be disabled in the *YAML view*, not in the *Form view*. To avoid any confusion, these settings have been removed from the *Form view*. They are still accessible in the *YAML view*. (link:https://issues.redhat.com/browse/NETOBSERV-1731[*NETOBSERV-1731*]) -* Previously, the eBPF agent was unable to clean up traffic control flows installed before an ungraceful crash, for example a crash due to a SIGTERM signal. This led to the creation of multiple traffic control flow filters with the same name, since the older ones were not removed. With this fix, all previously installed traffic control flows are cleaned up when the agent starts, before installing new ones. (link:https://issues.redhat.com/browse/NETOBSERV-1732[*NETOBSERV-1732*]) -* Previously, when configuring custom subnet labels and keeping the OpenShift subnets auto-detection enabled, OpenShift subnets would take precedence over the custom ones, preventing the definition of custom labels for in cluster subnets. With this fix, custom defined subnets take precedence, allowing the definition of custom labels for in cluster subnets. (link:https://issues.redhat.com/browse/NETOBSERV-1734[*NETOBSERV-1734*]) - -[id="network-observability-operator-release-notes-1-6_{context}"] -== Network Observability Operator 1.6.0 -The following advisory is available for the Network Observability Operator 1.6.0: - -* link:https://access.redhat.com/errata/RHSA-2024:3868[Network Observability Operator 1.6.0] - -[IMPORTANT] -===== -Before upgrading to the latest version of the Network Observability Operator, you must xref:../../observability/network_observability/installing-operators.adoc#network-observability-updating-migrating_network_observability[Migrate removed stored versions of the FlowCollector CRD]. An automated solution to this workaround is planned with link:https://issues.redhat.com/browse/NETOBSERV-1747[*NETOBSERV-1747*]. -===== - -[id="network-observability-operator-1.6.0-features-enhancements_{context}"] -=== New features and enhancements - -[id="network-observability-lokiless-enhancements-1.6_{context}"] -==== Enhanced use of Network Observability Operator without Loki -You can now use Prometheus metrics and rely less on Loki for storage when using the Network Observability Operator. For more information, see xref:../../observability/network_observability/installing-operators.adoc#network-observability-without-loki_network_observability[Network observability without Loki]. - -[id="network-observability-custom-metrics-1.6_{context}"] -==== Custom metrics API -You can create custom metrics out of flowlogs data by using the `FlowMetrics` API. Flowlogs data can be used with Prometheus labels to customize cluster information on your dashboards. You can add custom labels for any subnet that you want to identify in your flows and metrics. This enhancement can also be used to more easily identify external traffic by using the new labels `SrcSubnetLabel` and `DstSubnetLabel`, which exists both in flow logs and in metrics. Those fields are empty when there is external traffic, which gives a way to identify it. For more information, see xref:../../observability/network_observability/metrics-alerts-dashboards.adoc#network-observability-custom-metrics_metrics-dashboards-alerts[Custom metrics] and xref:../../observability/network_observability/flowmetric-api.adoc#flowmetric-flows-netobserv-io-v1alpha1[FlowMetric API reference]. - -[id="network-observability-eBPF-performance-enhancements-1.6_{context}"] -==== eBPF performance enhancements -Experience improved performances of the eBPF agent, in terms of CPU and memory, with the following updates: - -* The eBPF agent now uses TCX webhooks instead of TC. -* The *NetObserv / Health* dashboard has a new section that shows eBPF metrics. -** Based on the new eBPF metrics, an alert notifies you when the eBPF agent is dropping flows. -* Loki storage demand decreases significantly now that duplicated flows are removed. Instead of having multiple, individual duplicated flows per network interface, there is one de-duplicated flow with a list of related network interfaces. - -[IMPORTANT] -===== -With the duplicated flows update, the *Interface* and *Interface Direction* fields in the *Network Traffic* table are renamed to *Interfaces* and *Interface Directions*, so any bookmarked *Quick filter* queries using these fields need to be updated to `interfaces` and `ifdirections`. -===== - -For more information, see xref:../../observability/network_observability/network-observability-operator-monitoring.adoc#network-observability-netobserv-dashboard-ebpf-agent-alerts_network_observability[Using the eBPF agent alert] -and For more information, see xref:../../observability/network_observability/network-observability-overview.adoc#network-observability-dashboards_network-observability-overview[Network observability metrics dashboards] and xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-quickfilter_nw-observe-network-traffic[Filtering the network traffic]. - - -[id="network-observability-ebpf-collection-filtering-1.6_{context}"] -==== eBPF collection rule-based filtering -You can use rule-based filtering to reduce the volume of created flows. When this option is enabled, the *Netobserv / Health* dashboard for eBPF agent statistics has the *Filtered flows rate* view. For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-ebpf-flow-rule-filter_nw-observe-network-traffic[eBPF flow rule filter]. - -[id="network-observability-technology-preview-1.6_{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="network-observability-cli-1.6_{context}"] -==== Network Observability CLI -You can debug and troubleshoot network traffic issues without needing to install the Network Observability Operator by using the Network Observability CLI. Capture and visualize flow and packet data in real-time with no persistent storage requirement during the capture. For more information, see xref:../../observability/network_observability/netobserv_cli/netobserv-cli-install.adoc#network-observability-netoberv-cli-about_netobserv-cli-install[Network Observability CLI] and link:https://access.redhat.com/errata/RHEA-2024:3869[Network Observability CLI 1.6.0]. - -[id="network-observability-operator-1.6.0-bug-fixes_{context}"] -=== Bug fixes -* Previously, a dead link to the OpenShift containter platform documentation was displayed in the Operator Lifecycle Manager (OLM) form for the `FlowMetrics` API creation. Now the link has been updated to point to a valid page. (link:https://issues.redhat.com/browse/NETOBSERV-1607[*NETOBSERV-1607*]) -* Previously, the Network Observability Operator description in the Operator Hub displayed a broken link to the documentation. With this fix, this link is restored. (link:https://issues.redhat.com/browse/NETOBSERV-1544[*NETOBSERV-1544*]) -* Previously, if Loki was disabled and the Loki `Mode` was set to `LokiStack`, or if Loki manual TLS configuration was configured, the Network Observability Operator still tried to read the Loki CA certificates. With this fix, when Loki is disabled, the Loki certificates are not read, even if there are settings in the Loki configuration. (link:https://issues.redhat.com/browse/NETOBSERV-1647[*NETOBSERV-1647*]) -* Previously, the `oc` `must-gather` plugin for the Network Observability Operator was only working on the `amd64` architecture and failing on all others because the plugin was using `amd64` for the `oc` binary. Now, the Network Observability Operator `oc` `must-gather` plugin collects logs on any architecture platform. -* Previously, when filtering on IP addresses using `not equal to`, the Network Observability Operator would return a request error. -Now, the IP filtering works in both `equal` and `not equal to` cases for IP addresses and ranges. (link:https://issues.redhat.com/browse/NETOBSERV-1630[*NETOBSERV-1630*]) -* Previously, when a user was not an admin, the error messages were not consistent with the selected tab of the *Network Traffic* view in the web console. Now, the `user not admin` error displays on any tab with improved display.(link:https://issues.redhat.com/browse/NETOBSERV-1621[*NETOBSERV-1621*]) - -[id="network-observability-operator-1.6.0-known-issues_{context}"] -=== Known issues -* When the eBPF agent `PacketDrop` feature is enabled, and sampling is configured to a value greater than `1`, reported dropped bytes and dropped packets ignore the sampling configuration. While this is done on purpose to not miss any drops, a side effect is that the reported proportion of drops compared to non-drops becomes biased. For example, at a very high sampling rate, such as `1:1000`, it is likely that almost all the traffic appears to be dropped when observed from the console plugin. (link:https://issues.redhat.com/browse/NETOBSERV-1676[*NETOBSERV-1676*]) -* In the *Manage panels* pop-up window in the *Overview* tab, filtering on *total*, *bar*, *donut*, or *line* does not show any result. (link:https://issues.redhat.com/browse/NETOBSERV-1540[*NETOBSERV-1540*]) -* The SR-IOV secondary interface is not detected if the interface was created first and then the eBPF agent was deployed. It is only detected if the agent was deployed first and then the SR-IOV interface is created. (link:https://issues.redhat.com/browse/NETOBSERV-1697[*NETOBSERV-1697*]) -* When Loki is disabled, the *Topology* view in the OpenShift web console always shows the *Cluster* and *Zone* aggregation options in the slider beside the network topology diagram, even when the related features are not enabled. There is no specific workaround, besides ignoring these slider options. (link:https://issues.redhat.com/browse/NETOBSERV-1705[*NETOBSERV-1705*]) -* When Loki is disabled, and the OpenShift web console first loads, it might display an error: `Request failed with status code 400 Loki is disabled`. As a workaround, you can continue switching content on the *Network Traffic* page, such as clicking between the *Topology* and the *Overview* tabs. The error should disappear. (link:https://issues.redhat.com/browse/NETOBSERV-1706[*NETOBSERV-1706*]) - -[id="network-observability-operator-release-notes-1-5"] -== Network Observability Operator 1.5.0 -The following advisory is available for the Network Observability Operator 1.5.0: - -* link:https://access.redhat.com/errata/RHSA-2024:0853[Network Observability Operator 1.5.0] - -[id="network-observability-operator-1.5.0-features-enhancements"] -=== New features and enhancements - -[id="network-observability-dns-enhancements-1.5"] -==== DNS tracking enhancements -In 1.5, the TCP protocol is now supported in addition to UDP. New dashboards are also added to the *Overview* view of the Network Traffic page. For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-dns-overview_nw-observe-network-traffic[Configuring DNS tracking] and xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-dns-tracking_nw-observe-network-traffic[Working with DNS tracking]. - -[id="network-observability-RTT-1.5"] -==== Round-trip time (RTT) -You can use TCP handshake Round-Trip Time (RTT) captured from the `fentry/tcp_rcv_established` Extended Berkeley Packet Filter (eBPF) hookpoint to read smoothed round-trip time (SRTT) and analyze network flows. In the *Overview*, *Network Traffic*, and *Topology* pages in web console, you can monitor network traffic and troubleshoot with RTT metrics, filtering, and edge labeling. For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-RTT-overview_nw-observe-network-traffic[RTT Overview] and xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-RTT_nw-observe-network-traffic[Working with RTT]. - -[id="network-observability-metrics-dashboard-enhancements"] -==== Metrics, dashboards, and alerts enhancements -The network observability metrics dashboards in *Observe* → *Dashboards* → *NetObserv* have new metrics types you can use to create Prometheus alerts. You can now define available metrics in the `includeList` specification. In previous releases, these metrics were defined in the `ignoreTags` specification. For a complete list of these metrics, see xref:../../observability/network_observability/metrics-alerts-dashboards.adoc#network-observability-metrics_metrics-dashboards-alerts[Network observability metrics]. - -[id="network-observability-improved-lokistack-integration"] -==== Improvements for network observability without Loki -You can create Prometheus alerts for the *Netobserv* dashboard using DNS, Packet drop, and RTT metrics, even if you don't use Loki. In the previous version of network observability, 1.4, these metrics were only available for querying and analysis in the *Network Traffic*, *Overview*, and *Topology* views, which are not available without Loki. For more information, see xref:../../observability/network_observability/metrics-alerts-dashboards.adoc#network-observability-metrics_metrics-dashboards-alerts[Network observability metrics] - -[id="network-observability-zones"] -==== Availability zones -You can configure the `FlowCollector` resource to collect information about the cluster availability zones. This configuration enriches the network flow data with the link:https://kubernetes.io/docs/reference/labels-annotations-taints/#topologykubernetesiozone[`topology.kubernetes.io/zone`] label value applied to the nodes. For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-zones_nw-observe-network-traffic[Working with availability zones]. - -[id="network-observability-enhanced-configuration-and-ui-1.5"] -==== Notable enhancements -The 1.5 release of the Network Observability Operator adds improvements and new capabilities to the {product-title} web console plugin and the Operator configuration. - -[id="performance-enhancements-1.5_{context}"] -===== Performance enhancements -* The `spec.agent.ebpf.kafkaBatchSize` default is changed from `10MB` to `1MB` to enhance eBPF performance when using Kafka. -+ -[IMPORTANT] -===== -When upgrading from an existing installation, this new value is not set automatically in the configuration. If you monitor a performance regression with the eBPF Agent memory consumption after upgrading, you might consider reducing the `kafkaBatchSize` to the new value. -===== - -[id="web-console-enhancements-1.5_{context}"] -===== Web console enhancements: - -* There are new panels added to the *Overview* view for DNS and RTT: Min, Max, P90, P99. -* There are new panel display options added: -** Focus on one panel while keeping others viewable but with smaller focus. -** Switch graph type. -** Show *Top* and *Overall*. -* A collection latency warning is shown in the *Custom time range* pop-up window. -* There is enhanced visibility for the contents of the *Manage panels* and *Manage columns* pop-up windows. -* The Differentiated Services Code Point (DSCP) field for egress QoS is available for filtering QoS DSCP in the web console *Network Traffic* page. - -[id="configuration-enhancements-1.5_{context}"] -===== Configuration enhancements: - -* The `LokiStack` mode in the `spec.loki.mode` specification simplifies installation by automatically setting URLs, TLS, cluster roles and a cluster role binding, as well as the `authToken` value. The `Manual` mode allows more control over configuration of these settings. -* The API version changes from `flows.netobserv.io/v1beta1` to `flows.netobserv.io/v1beta2`. - -[id="network-observability-operator-1.5.0-bug-fixes"] -=== Bug fixes - -* Previously, it was not possible to register the console plugin manually in the web console interface if the automatic registration of the console plugin was disabled. If the `spec.console.register` value was set to `false` in the `FlowCollector` resource, the Operator would override and erase the plugin registration. -With this fix, setting the `spec.console.register` value to `false` does not impact the console plugin registration or registration removal. As a result, the plugin can be safely registered manually. (link:https://issues.redhat.com/browse/NETOBSERV-1134[*NETOBSERV-1134*]) -* Previously, using the default metrics settings, the *NetObserv/Health* dashboard was showing an empty graph named *Flows Overhead*. This metric was only available by removing "namespaces-flows" and "namespaces" from the `ignoreTags` list. With this fix, this metric is visible when you use the default metrics setting. (link:https://issues.redhat.com/browse/NETOBSERV-1351[*NETOBSERV-1351*]) -* Previously, the node on which the eBPF Agent was running would not resolve with a specific cluster configuration. This resulted in cascading consequences that culminated in a failure to provide some of the traffic metrics. With this fix, the eBPF agent's node IP is safely provided by the Operator, inferred from the pod status. Now, the missing metrics are restored. (link:https://issues.redhat.com/browse/NETOBSERV-1430[*NETOBSERV-1430*]) -* Previously, the Loki error 'Input size too long' error for the Loki Operator did not include additional information to troubleshoot the problem. -With this fix, help is directly displayed in the web console next to the error with a direct link for more guidance. (link:https://issues.redhat.com/browse/NETOBSERV-1464[*NETOBSERV-1464*]) -* Previously, the console plugin read timeout was forced to 30s. -With the `FlowCollector` `v1beta2` API update, you can configure the `spec.loki.readTimeout` specification to update this value according to the Loki Operator `queryTimeout` limit. (link:https://issues.redhat.com/browse/NETOBSERV-1443[*NETOBSERV-1443*]) -* Previously, the Operator bundle did not display some of the supported features by CSV annotations as expected, such as `features.operators.openshift.io/...` -With this fix, these annotations are set in the CSV as expected. (link:https://issues.redhat.com/browse/NETOBSERV-1305[*NETOBSERV-1305*]) -* Previously, the `FlowCollector` status sometimes oscillated between `DeploymentInProgress` and `Ready` states during reconciliation. -With this fix, the status only becomes `Ready` when all of the underlying components are fully ready. (link:https://issues.redhat.com/browse/NETOBSERV-1293[*NETOBSERV-1293*]) - -[id="network-observability-operator-1.5.0-known-issue"] -=== Known issues -* When trying to access the web console, cache issues on OCP 4.14.10 prevent access to the *Observe* view. The web console shows the error message: `Failed to get a valid plugin manifest from /api/plugins/monitoring-plugin/`. The recommended workaround is to update the cluster to the latest minor version. If this does not work, you need to apply the workarounds described in this link:https://access.redhat.com/solutions/7052408[Red Hat Knowledgebase article].(link:https://issues.redhat.com/browse/NETOBSERV-1493[*NETOBSERV-1493*]) - -* Since the 1.3.0 release of the Network Observability Operator, installing the Operator causes a warning kernel taint to appear. The reason for this error is that the network observability eBPF agent has memory constraints that prevent preallocating the entire hashmap table. The Operator eBPF agent sets the `BPF_F_NO_PREALLOC` flag so that pre-allocation is disabled when the hashmap is too memory expansive. - -[id="network-observability-operator-release-notes-1-4-2"] -== Network Observability Operator 1.4.2 -The following advisory is available for the Network Observability Operator 1.4.2: - -* link:https://access.redhat.com/errata/RHSA-2023:6787[2023:6787 Network Observability Operator 1.4.2] - -=== CVEs -* link:https://access.redhat.com/security/cve/CVE-2023-39325[2023-39325] -* link:https://access.redhat.com/security/cve/CVE-2023-44487[2023-44487] - -[id="network-observability-operator-release-notes-1-4-1"] -== Network Observability Operator 1.4.1 -The following advisory is available for the Network Observability Operator 1.4.1: - -* link:https://access.redhat.com/errata/RHSA-2023:5974[2023:5974 Network Observability Operator 1.4.1] - -=== CVEs -* link:https://access.redhat.com/security/cve/cve-2023-44487[2023-44487] -* link:https://access.redhat.com/security/cve/cve-2023-39325[2023-39325] -* link:https://access.redhat.com/security/cve/cve-2023-29406[2023-29406] -* link:https://access.redhat.com/security/cve/CVE-2023-29409[2023-29409] -* link:https://access.redhat.com/security/cve/cve-2023-39322[2023-39322] -* link:https://access.redhat.com/security/cve/cve-2023-39318[2023-39318] -* link:https://access.redhat.com/security/cve/cve-2023-39319[2023-39319] -* link:https://access.redhat.com/security/cve/cve-2023-39321[2023-39321] - -=== Bug fixes - -* In 1.4, there was a known issue when sending network flow data to Kafka. The Kafka message key was ignored, causing an error with connection tracking. Now the key is used for partitioning, so each flow from the same connection is sent to the same processor. (link:https://issues.redhat.com/browse/NETOBSERV-926[*NETOBSERV-926*]) - -* In 1.4, the `Inner` flow direction was introduced to account for flows between pods running on the same node. Flows with the `Inner` direction were not taken into account in the generated Prometheus metrics derived from flows, resulting in under-evaluated bytes and packets rates. -Now, derived metrics are including flows with the `Inner` direction, providing correct bytes and packets rates. (link:https://issues.redhat.com/browse/NETOBSERV-1344[*NETOBSERV-1344*]) diff --git a/observability/network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc b/observability/network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc index 0ebcf3b1eb64..ea99afb829a5 100644 --- a/observability/network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc +++ b/observability/network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc @@ -24,7 +24,14 @@ include::modules/network-observability-operator-release-notes-1-9-2-bug-fixes.ad //netobserv 1.9.0 //netobserv 1.8.1 //netobserv 1.8.0 -//netobserv 1.7.0 + +include::modules/network-observability-operator-release-notes-1-7-0.adoc[leveloffset=+1] + +include::modules/network-observability-operator-release-notes-1-7-0-new-features-and-enhancements.adoc[leveloffset=+1] + +include::modules/network-observability-operator-release-notes-1-7-0-fixed-issues.adoc[leveloffset=+1] + +include::modules/network-observability-operator-release-notes-1-7-0-known-issues.adoc[leveloffset=+1] include::modules/network-observability-operator-release-notes-1-6-2.adoc[leveloffset=+1]