Uploaded image for project: 'OpenShift Windows Containers'
  1. OpenShift Windows Containers
  2. WINC-666

Investigate creating external network switch

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • 3
    • False
    • False
    • undefined
    • WinC - Sprint 211

      From upstream, I discovered that there is an issue where the first container that comes has a network blip due to the time taken by CNI / kube-proxy to create the first external network switch. The workaround apparently is to create a dummy network switch to prevent this flip from happening. We should investigate if this helps us as we sometimes see flakes in our east west networking tests.

      Upstream Slack thread for code references

            jvaldes@redhat.com Jose Valdes
            paravindh Aravindh Puthiyaparambil
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: