Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-66

CNO: watch for OvS ConfigMap

XMLWordPrintable

    • Upstream
    • 5
    • False
    • False
    • Hide
      - CNO can read the configmap that describes the desired ovs config
      - CNO watches for changes
      - Resulting ovn pods have the corresponding environment variables set up
      Show
      - CNO can read the configmap that describes the desired ovs config - CNO watches for changes - Resulting ovn pods have the corresponding environment variables set up
    • NetObserv - Sprint 209, NetObserv - Sprint 210, NetObserv - Sprint 211, NetObserv - Sprint 212

      As described in this enhancement [*], we need to bring changes to the Cluster Network Operator so that it watches for a config map and propagate that configuration to the ovn pods.

      Ultimately, this config map will be generated by the network observability operator (but whoever create this config map shouldn't change anything for the CNO, it can be created manually as well)

              mmaciasl@redhat.com Mario Macias (Inactive)
              jtakvori Joel Takvorian
              Jean Chen Jean Chen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: