Hello. I'm trying to determine how the "providerID" is being set. Briefly, we have deployed the AWS Load Balancer Controller into a RKE2 cluster, and can provision a load balancer, but error (typical): "providerID rke2://ip-xxx-xxx-xxx-xxx.<domain> is invalid for EC2 instances, node: <http://ip-xxx-xxx-xxx-xxx.calormen.net|ip-xxx-xxx-xxx-xxx.<>domain>" is reported in the controller pods. I suspected the problem might be related to the IP-based hostname / instance ID limitation discussed here: https://github.com/kubernetes/cloud-provider-aws/blob/master/docs/prerequisites.md so I launched an instance with hostname "ip-xxx-xxx-xxx-xxx.<region>.compute.internal", installed the RKE2 agent, and joined it to the cluster. The node name is "correct" (the IP-based hostname), but there was no change in behavior. Error: "providerID rke2://ip-xxx-xxx-xxx-xxx.us-gov-west-1.compute.internal is invalid for EC2 instances, node: ip-xxx-xxx-xxx-xxx.us-gov-west-1.compute.internal" I'd like to

We had a general question regarding Rancher Federal. Is it possible to spin up a RKE2 cluster from the Rancher UI?