Install the Network Observability Operator
Install the Network Observability Operator and use the setup wizard to create the FlowCollector custom resource definition (CRD) to complete the initial configuration.
You can set specifications in the web console when you create the FlowCollector.
|
|
The actual memory consumption of the Operator depends on your cluster size and the number of resources deployed. Memory consumption might need to be adjusted accordingly. For more information refer to "Network Observability controller manager pod runs out of memory" in the "Important Flow Collector configuration considerations" section. |
-
If you choose to use Loki, install the Loki Operator version 5.7+.
-
You must have
cluster-adminprivileges. -
One of the following supported architectures is required:
amd64,ppc64le,arm64, ors390x. -
Any CPU supported by Red Hat Enterprise Linux (RHEL) 9.
-
Must be configured with OVN-Kubernetes as the main network plugin, and optionally using secondary interfaces with Multus and SR-IOV.
|
|
Additionally, this installation example uses the |
-
In the OpenShift Container Platform web console, click Ecosystem → Software Catalog.
-
Choose Network Observability Operator from the list of available Operators in the software catalog, and click Install.
-
Select the checkbox
Enable Operator recommended cluster monitoring on this Namespace. -
Navigate to Operators → Installed Operators. Under Provided APIs for Network Observability, select the Flow Collector link.
-
Follow the Network Observability FlowCollector setup wizard.
-
Click Create.
To confirm this was successful, when you navigate to Observe you should see Network Traffic listed in the options.
In the absence of Application Traffic within the OpenShift Container Platform cluster, default filters might show that there are "No results", which results in no visual flow. Beside the filter selections, select Clear all filters to see the flow.