Rancher RKE2 Cluster in AWS - Target Group Empty due to providerID invalid error

[albertmorenomng]

Hello,

Deployed Rancher RKE2 cluster in AWS using Amazon EC2 nodes with CloudProvider set to "RKE2 Embeded". Not EKS Cluster.
Installed aws load balancer controller version v2.10.1 (chart version 1.10.1)

Creating ingress, the controller creates sucessfully Load Balancer and Target Group, but the Target Group is empty (no instances inside), logs from ALB controller shows this messages:

{"level":"error","ts":"2024-12-10T15:11:34Z","msg":"Reconciler error","controller":"targetGroupBinding","controllerGroup":"elbv2.k8s.aws",
"controllerKind":"TargetGroupBinding","TargetGroupBinding":{"name":"k8s-game2048-service2-59aeb62d97","namespace":"game-2048"},"namespace":"game-2048","name":"k8s-game2048-service2-59aeb62d97","reconcileID":"3d2fe906-09e7-4be6-8869-87fcc2e72d14","error":"providerID rke2://amazonec2-workerpool01-9gxf5-fmnsm is invalid for EC2 instances, node: amazonec2-workerpool01-9gxf5-fmnsm"}

It seems that the controller dos not reconize tghe providerID.

Any ideas how to solve it? Is this a bug?

Regards

[shraddhabang]

We dont support this cloudprovider yet, Will you be able to use EC2 instead?

[albertmorenomng]

Thanks @shraddhabang

At this moment we can not use ec2 type.

Did you know aprox when rke2 cloudpriver will be supported? Is it in your roadmap?

Regards

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten