-
Task
-
Resolution: Done
-
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.
- is related to
-
OCPBUGS-7784 Pod_DNS_Resolution test fails frequently in CI
- Closed
-
WINC-720 Windows packet tracing in CI
- Closed