Christian Schlotter

You should be able to take a look at the ResizedCondition of a KCP: https://github.com/kubernetes-sigs/cluster-api/blob/88905d4349f793db458b719e9844ba7960ed2004/controlplane/kubeadm/api/v1beta1/condition_consts.go#L61 It is getting set here: https://github.com/kubernetes-sigs/cluster-api/blob/88905d4349f793db458b719e9844ba7960ed2004/controlplane/kubeadm/internal/controllers/status.go#L65-L86 And from quickly reading it, the condition should either...

Good question, maybe searching the PRs which introduced the one or the other or the ones for the proposals and reading through them may have context on that.

Could you take a look on why `vsphere-csi-controller-664c45f69b-6ddz4` is in `Pending`? (via `kubectl describe pod`)? If I got it right this pod needs to be up first so the daemonset...

So something prevents the vsphere-csi-controller from getting scheduled. There may be taints or something else why this happens. You need to figure out why that is and then the daemonset...

Would be interesting to figure out together with https://github.com/kubernetes/cloud-provider-vsphere where the gaps are that both can run at the same time. (for CSI we simply consume the above).

Thanks @Dhairya-Arora01 for kicking this off. Closing here in favour of: - #11174 /close

Note: I tried to address all comments at #11174

/assign PatrickLaabs

/ok-to-test

/remove-area provider/infrastructure-in-memory