-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #65471 from openshift-cherrypick-robot/cherry-pick…
…-64448-to-enterprise-4.13 [enterprise-4.13] OCPBUGS-17785: Document SR-IOV/FlowCollector config
- Loading branch information
Showing
4 changed files
with
45 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
// Module included in the following assemblies: | ||
// | ||
// * network_observability/configuring-operator.adoc | ||
|
||
:_content-type: PROCEDURE | ||
[id="network-observability-SR-IOV-config_{context}"] | ||
= Configuring monitoring for SR-IOV interface traffic | ||
In order to collect traffic from a cluster with a Single Root I/O Virtualization (SR-IOV) device, you must set the `FlowCollector` `spec.agent.ebpf.privileged` field to `true`. Then, the eBPF agent monitors other network namespaces in addition to the host network namespaces, which are monitored by default. When a pod with a virtual functions (VF) interface is created, a new network namespace is created. With `SRIOVNetwork` policy `IPAM` configurations specified, the VF interface is migrated from the host network namespace to the pod network namespace. | ||
|
||
.Prerequisites | ||
* Access to an {product-title} cluster with a SR-IOV device. | ||
* The `SRIOVNetwork` custom resource (CR) `spec.ipam` configuration must be set with an IP address from the range that the interface lists or from other plugins. | ||
.Procedure | ||
. In the web console, navigate to *Operators* -> *Installed Operators*. | ||
. Under the *Provided APIs* heading for the *NetObserv Operator*, select *Flow Collector*. | ||
. Select *cluster* and then select the *YAML* tab. | ||
. Configure the `FlowCollector` custom resource. A sample configuration is as follows: | ||
+ | ||
[id="network-observability-flowcollector-configuring-SRIOV-monitoring{context}"] | ||
.Configure `FlowCollector` for SR-IOV monitoring | ||
[source,yaml] | ||
---- | ||
apiVersion: flows.netobserv.io/v1alpha1 | ||
kind: FlowCollector | ||
metadata: | ||
name: cluster | ||
spec: | ||
namespace: netobserv | ||
deploymentModel: DIRECT | ||
agent: | ||
type: EBPF | ||
ebpf: | ||
privileged: true <1> | ||
---- | ||
<1> The `spec.agent.ebpf.privileged` field value must be set to `true` to enable SR-IOV monitoring. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters