This message was deleted.

Hi, this might be a bug, https://github.com/rancher-sandbox/cluster-api-provider-rke2/commit/9d2654a4ca547442a877500a79cddcf827ecdb04#diff-87863bb6eae79[…]4f7525c331a8b7L167 - @cool-thailand-26552 do you remember why we introduced this change?

Yes, the

DisableCloudController

flag is for RKE2's default cloud controller manager (see corresponding flag in this page), which is incompatible with out-of-tree cloud controllers. Indeed, during the provisioning of an AWS cloud controller for instance, the `cloudProvider`field on the nodes of the workload cluster will indicate "rke2" whereas it should be "external". And, this causes CAPI to be stuck waiting for it to be ready.

Could it be possible to add an option to configure cloud-controller ?

Yes, it is already the case in the code snippet mentioned above by @astonishing-stone-14417. However, there is indeed a bug, which is in the default behaviour here.

should we add it back to the switch case? so by default DisableCloudController is false and can be disabled if needed? We can document it on examples page

Well, I think the only place that has to change is the default value, the other part in your snippet should be the right value