OSDOCS-16180 [NETOBSERV] Add sentence about configuring using console plugin

Author: gwynnemonahan

modules/network-observability-flowcollector-view.adoc

@@ -6,7 +6,7 @@
 [id="network-observability-flowcollector-view_{context}"]
 = View the FlowCollector resource
 
-You can view and edit YAML directly in the {product-title} web console.
+The `FlowCollector` resource can be viewed and modified in the {product-title} web console through the integrated setup, advanced form, or by editing the YAML directly.
 
 .Procedure
 . In the web console, navigate to *Ecosystem* -> *Installed Operators*.

modules/network-observability-operator-install.adoc

@@ -31,15 +31,8 @@ Additionally, this installation example uses the `netobserv` namespace, which is
 . 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 *Ecosystem* -> *Installed Operators*. Under Provided APIs for Network Observability, select the *Flow Collector* link.
-. Navigate to the *Flow Collector* tab, and click *Create FlowCollector*. Make the following selections in the form view:
-.. *spec.agent.ebpf.Sampling*: Specify a sampling size for flows. Lower sampling sizes will have higher impact on resource utilization. For more information, see the "FlowCollector API reference", `spec.agent.ebpf`.
-.. If you are not using Loki, click *Loki client settings* and change *Enable* to *False*. The setting is *True* by default.
-.. If you are using Loki, set the following specifications:
-... *spec.loki.mode*: Set this to the `LokiStack` mode, which automatically sets URLs, TLS, cluster roles and a cluster role binding, as well as the `authToken` value. Alternatively, the `Manual` mode allows more control over configuration of these settings.
-... *spec.loki.lokistack.name*: Set this to the name of your `LokiStack` resource. In this documentation, `loki` is used.
-.. Optional: If you are in a large-scale environment, consider configuring the `FlowCollector` with Kafka for forwarding data in a more resilient, scalable way. See "Configuring the Flow Collector resource with Kafka storage" in the "Important Flow Collector configuration considerations" section.
-.. Optional: Configure other optional settings before the next step of creating the `FlowCollector`. For example, if you choose not to use Loki, then you can configure exporting flows to Kafka or IPFIX. See "Export enriched network flow data to Kafka and IPFIX" and more in the "Important Flow Collector configuration considerations" section.
+. 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