k8s-1.19 and -1.20: uninitialized not cleared by OCCM

Created by: garloff

The coredns pods stay in "pending" state. The reason is that k8s sets a taint node.cloudprovider.kubernetes.io/uninitialized=true:NoSchedule when an external cloud provider is used. It stays in this state until the cloud-controller-manager comes along and clears it. Only then can most of the initialization proceed ... The occm versions that are meant for k8s-1.19 and 1.20 apparently do not expect to be used as external CCM and thus do not clear the flag. Newer occm versions do ...