Open anmazzotti opened 4 months ago
By briefly looking into our API and comparing it to CAPI's kubeadm, I observed the following divergance within our API:
RKE2ControlPlaneSpec.InfrastructureRef
even though it is already part of the RKE2ControlPlaneSpec.MachineTemplate
. That is not the case with kubeadmRKE2ControlPlaneSpec
from RKE2ControlPlaneTemplateResource.Spec
where it should refer to RKE2ControlPlaneTemplateResourceSpec
instead (simply because we don't have that API struct for some reason), similar to what kubeadm exposesThis issue is stale because it has been open 90 days with no activity.
What happened: When defining my RKE2 cluster class I configured the
RKE2ControlPlaneTemplate
as follows:In the CC definition the
spec.controlPlane.machineInfrastructure.ref
is correctly set:However RKE2 provider fails to initialize the control plane machines:
The workaround is to repeat the
infrastructureRef
in theRKE2ControlPlaneTemplate
, like this:I think this should not be necessary due to the CC definition.
What did you expect to happen:
The RKE2ControlPlaneTemplate should respect what was defined in the Cluster Class.
How to reproduce it:
See config above, or it can be reproduced with the quickstart sample by removing the
RKE2ControlPlaneTemplate.spec.template.spec.infrastructureRef
object. referenceAnything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
/etc/os-release
):