Skip to content

Commit 60c3a81

Browse files
committed
OSDOCS-10882 [NETOBSERV] bpfman Support TP
1 parent 628014d commit 60c3a81

File tree

2 files changed

+46
-0
lines changed

2 files changed

+46
-0
lines changed
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * network_observability/observing-network-traffic.adoc
4+
5+
:_mod-docs-content-type: PROCEDURE
6+
[id="network-observability-ebpf-manager-operator_{context}"]
7+
= Working with the eBPF Manager Operator
8+
9+
The eBPF Manager Operator reduces the attack surface and ensures compliance, security, and conflict prevention by managing all eBPF programs. Network observability can use the eBPF Manager Operator to load hooks. As a result, you no longer need to provide the eBPF Agent with privileged mode or additional Linux capabilities such as `CAP_BPF` and `CAP_PERFMON`. The eBPF Manager Operator with network observability is only supported on 64-bit AMD architecture.
10+
11+
:FeatureName: eBPF Manager Operator with network observability
12+
include::snippets/technology-preview.adoc[]
13+
14+
.Procedure
15+
. In the web console, navigate to *Operators* -> *Operator Hub*.
16+
. Install *eBPF Manager*.
17+
. Check *Workloads* -> *Pods* in the `bpfman` namespace to make sure they are all up and running.
18+
. Configure the `FlowCollector` custom resource to use the eBPF Manager Operator:
19+
+
20+
.Example `FlowCollector` configuration
21+
[source,yaml]
22+
----
23+
apiVersion: flows.netobserv.io/v1beta2
24+
kind: FlowCollector
25+
metadata:
26+
name: cluster
27+
spec:
28+
agent:
29+
ebpf:
30+
features:
31+
- EbpfManager
32+
----
33+
34+
.Verification
35+
. In the web console, navigate to *Operators* -> *Installed Operators*.
36+
. Click *eBPF Manager Operator* -> *All instances* tab.
37+
+
38+
For each node, verify that a `BpfApplication` named `netobserv` and a pair of `BpfProgram` objects, one for Traffic Control (TCx) ingress and another for TCx egress, exist. If you enable other eBPF Agent features, you might have more objects.

observability/network_observability/observing-network-traffic.adoc

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,6 +69,14 @@ include::modules/network-observability-working-with-conversations.adoc[leveloffs
6969
include::modules/network-observability-packet-drops.adoc[leveloffset=+2]
7070
include::modules/network-observability-dns-tracking.adoc[leveloffset=+2]
7171
include::modules/network-observability-RTT.adoc[leveloffset=+2]
72+
include::modules/network-observability-ebpf-manager-operator.adoc[leveloffset=+2]
73+
74+
//eBPF Manager Operator in OCP > Networking
75+
[role="_additional-resources"]
76+
.Additional resources
77+
* xref:../../networking/networking_operators/ebpf_manager/ebpf-manager-operator-install.adoc[Installing the eBPF Manager Operator]
78+
79+
//Traffic flows continued
7280
include::modules/network-observability-histogram-trafficflow.adoc[leveloffset=+2]
7381
include::modules/network-observability-working-with-zones.adoc[leveloffset=+2]
7482
include::modules/network-observability-filtering-ebpf-rule.adoc[leveloffset=+2]

0 commit comments

Comments
 (0)