Network Observability Operator in OKD

    The Network Observability Operator provides the Flow Collector API. When a Flow Collector resource is created, it deploys pods and services to create and store network flows in the Loki log store, as well as to display dashboards, metrics, and flows in the OKD web console.

    Procedure

    1. Run the following command to view the state of :

      Example output

      1. NAME      AGENT   SAMPLING (EBPF)   DEPLOYMENT MODEL   STATUS
      2. cluster   EBPF    50                DIRECT             Ready
      1. $ oc get pods -n netobserv

      Example output

    flowlogs-pipeline pods collect flows, enriches the collected flows, then send flows to the Loki storage. netobserv-plugin pods create a visualization plugin for the OKD Console.

    1. Check the status of pods running in the namespace netobserv-privileged by entering the following command:

      1. $ oc get pods -n netobserv-privileged

      Example output

      1. NAME                         READY   STATUS    RESTARTS   AGE
      2. netobserv-ebpf-agent-6gbrk   1/1     Running   0          151m
      4. netobserv-ebpf-agent-vrcnf   1/1     Running   0          151m
      5. netobserv-ebpf-agent-xf5jh   1/1     Running   0          151m

    1. If you are using a Loki Operator, check the status of pods running in the openshift-operators-redhat namespace by entering the following command:

      Example output

      1. NAME                                                READY   STATUS    RESTARTS   AGE
      2. loki-operator-controller-manager-5f6cff4f9d-jq25h   2/2     Running   0          18h
      3. lokistack-compactor-0                               1/1     Running   0          18h
      4. lokistack-distributor-654f87c5bc-qhkhv              1/1     Running   0          18h
      5. lokistack-distributor-654f87c5bc-skxgm              1/1     Running   0          18h
      7. lokistack-index-gateway-1                           1/1     Running   0          18h
      8. lokistack-ingester-0                                1/1     Running   0          18h
      9. lokistack-ingester-1                                1/1     Running   0          18h
      10. lokistack-ingester-2                                1/1     Running   0          18h
      11. lokistack-querier-66747dc666-6vh5x                  1/1     Running   0          18h
      12. lokistack-querier-66747dc666-cjr45                  1/1     Running   0          18h
      13. lokistack-querier-66747dc666-xh8rq                  1/1     Running   0          18h
      14. lokistack-query-frontend-85c6db4fbd-b2xfb           1/1     Running   0          18h
      15. lokistack-query-frontend-85c6db4fbd-jm94f           1/1     Running   0          18h

    Viewing Network Observability Operator status and configuration

    You can inspect the status and view the details of the FlowCollector using the oc describe command.

    Procedure