From a014cc7754f983d70b9f3dc23019171e1cd829fe Mon Sep 17 00:00:00 2001 From: Maria Aldinger Date: Sat, 14 Oct 2023 17:38:15 -0400 Subject: [PATCH] GH#65938: fixes typo duplicate the --- modules/network-observability-architecture.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/network-observability-architecture.adoc b/modules/network-observability-architecture.adoc index 6e2b6bceca..e1d5dc484e 100644 --- a/modules/network-observability-architecture.adoc +++ b/modules/network-observability-architecture.adoc @@ -8,7 +8,7 @@ The Network Observability Operator provides the `FlowCollector` API, which is instantiated at installation and configured to reconcile the `eBPF agent`, the `flowlogs-pipeline`, and the `netobserv-plugin` components. Only a single `FlowCollector` per cluster is supported. -The `eBPF agent` runs on each cluster node with some privileges to collect network flows. The `flowlogs-pipeline` receives the network flows data and enriches the data with Kubernetes identifiers. If you are using Loki, the `flowlogs-pipeline` sends flow logs data to Loki for storing and indexing. The `netobserv-plugin`, which is a dynamic {product-title} web console plugin, queries Loki to fetch network flows data. Cluster-admins can view the the data in the web console. +The `eBPF agent` runs on each cluster node with some privileges to collect network flows. The `flowlogs-pipeline` receives the network flows data and enriches the data with Kubernetes identifiers. If you are using Loki, the `flowlogs-pipeline` sends flow logs data to Loki for storing and indexing. The `netobserv-plugin`, which is a dynamic {product-title} web console plugin, queries Loki to fetch network flows data. Cluster-admins can view the data in the web console. image::network-observability-architecture.png[Network Observability eBPF export architecture]