mirror of
https://github.com/k3s-io/kubernetes.git
synced 2026-01-29 21:29:24 +00:00
1a510a1bec
As discussed in https://github.com/kubernetes/kubernetes/pull/93658, relying on a watch to deliver all events is not acceptable, not even for a test, because it can and did (at least for OpenShift testing) to test flakes. The solution in #93658 was to replace log flooding with a clear test failure, but that didn't solve the flakiness. A better solution is to use a RetryWatcher which "under normal circumstances" (https://github.com/kubernetes/kubernetes/pull/93777#discussion_r467932080) should always deliver all changes.