mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
43 lines
2.5 KiB
Plaintext
43 lines
2.5 KiB
Plaintext
// Module included in the following assemblies:
|
|
|
|
// * networking/network_observability/installing-operators.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="network-observability-operator-installation_{context}"]
|
|
= Installing the Network Observability Operator
|
|
|
|
You can install the Network Observability Operator using the {product-title} web console Operator Hub. When you install the Operator, it provides the `FlowCollector` custom resource definition (CRD). You can set specifications in the web console when you create the `FlowCollector`.
|
|
|
|
[IMPORTANT]
|
|
====
|
|
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.
|
|
====
|
|
|
|
.Prerequisites
|
|
|
|
* If you choose to use Loki, install the link:https://catalog.redhat.com/software/containers/openshift-logging/loki-rhel8-operator/622b46bcae289285d6fcda39[{loki-op} version 5.7+].
|
|
* You must have `cluster-admin` privileges.
|
|
* One of the following supported architectures is required: `amd64`, `ppc64le`, `arm64`, or `s390x`.
|
|
* 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.
|
|
|
|
[NOTE]
|
|
====
|
|
Additionally, this installation example uses the `netobserv` namespace, which is used across all components. You can optionally use a different namespace.
|
|
====
|
|
|
|
.Procedure
|
|
|
|
. In the {product-title} 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*.
|
|
|
|
.Verification
|
|
|
|
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 {product-title} 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.
|