You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: