add uninitialized toleration

nodes are tainted with node.cloudprovider.kubernetes.io/uninitialized
because we set cloudProvider: external.

this prevents some crucial pods from being scheduled (for example
we need the kube-vip pod to start on the first node so it can
announce the control plane IP)

templates/vsphere/cluster_template.yaml

@@ -117,6 +117,10 @@ spec:
             name: kube-vip
             namespace: kube-system
           spec:
+            tolerations:
+              - key: "node.cloudprovider.kubernetes.io/uninitialized"
+                operator: "Exists"
+                effect: "NoSchedule"
             containers:
             - args:
               - manager
@@ -896,6 +900,10 @@ data:
           - effect: NoSchedule
             key: node-role.kubernetes.io/control-plane
             operator: Exists
+          #https://github.com/kubernetes-sigs/vsphere-csi-driver/issues/2284
+          - key: node.cloudprovider.kubernetes.io/uninitialized
+            value: "true"
+            effect: NoSchedule
           volumes:
           - name: vsphere-config-volume
             secret: