This message was deleted.

added cloud-config and cloud.conf file to my control plane nodes, when I restart the rke2-server service it seems to rejoin with a duplicate node

By “added’, do you mean that you changed the cloud-provider after starting RKE2 for the first time? If so, you shouldn’t do that. You should ensure that the cloud-provider is configured correctly before initially starting the nodes. The nodes get a bunch of annotations on them that bind them to a particular cloud-provider, if you change that after the fact it will both change the node name (to match the nodename required by the cloud provider) and so that it can create a new node with the proper cloud-provider ID and type.

ah, yes added to existing cluster so that explains it, thanks!

correct. the

cloud-provider-name: aws

option is just passed through to the core Kubernetes components, and the code that supported that option value has been removed from Kubernetes. Users should plan on migrating to the out-of-tree cloud provider on 1.26, before upgrading to 1.27