Uploaded image for project: 'OpenShift Core Networking'
  1. OpenShift Core Networking
  2. CORENET-6261

Avoid multus NAD webhook race with ovn-kubernetes default NAD creation on install

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • None
    • None
    • CORENET Sprint 275, CORENET Sprint 276

      Add CEL expression to ignore default/openshift-ovn-kubernetes NAD to prevent circular dependency where ovn-k fails to start because multus webhook blocks NAD creation, while webhook uses cluster-networked pdos which require ovn-k to be running.

      Order of events on install:

      1. OVN-Kubernetes and Multus manifests(webhook included) get applied.
      2. OVN-Kubernetes starts and tries to apply the default NAD but fails because the webhook is not running:
      failed to run ovnkube: failed to start cluster manager: failed to ensure default network nad exists: Internal error occurred: failed calling webhook "multus-validating-config.k8s.io": failed to call webhook: Post "https://multus-admission-controller.openshift-multus.svc:443/validate?timeout=30s": no endpoints available for service "multus-admission-controller" 
      1. Multus webhook doesn't start because it is a cluster-networked deployment so it depends on ovn-k being up.

              pdiak@redhat.com Patryk Diak
              pdiak@redhat.com Patryk Diak
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: