Once the rebase (1.19) PR lands https://github.com/openshift/kubernetes/pull/325 the fixes (https://github.com/openshift/origin/pull/25489 and https://github.com/openshift/origin/pull/25490) will be present in 4.6.
(In reply to Lukasz Szaszkiewicz from comment #1)
> Once the rebase (1.19) PR lands
> https://github.com/openshift/kubernetes/pull/325 the fixes
> (https://github.com/openshift/origin/pull/25489 and
> https://github.com/openshift/origin/pull/25490) will be present in 4.6.
Hi Lukasz, PR 25489 and 25490 have not been merged, could you have a look? without them merging, versification is unable to go on.
CC: email@example.com, PR 25489 and 25490 are 4.5 fixes, we need corresponding fixes for 4.6 here.
OCP 4.6 already has been re-based bump to kube 1.19 and have a master node connected to the cluster. Then, disconnect it from the network for 5 minutes, after network recovery kubelet reconnects to the Apiserver as before. Then observe kubelet's logs, such timeouts do not occur anymore.
# cat ~/test.sh
ifconfig ens5 down
ifconfig ens5 up
# grep -nr 'Timeout: Too large resource version' openshift-*
# journalctl -b -u kubelet | grep 'Timeout: Too large resource version'
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.