Back-off restarting failed container error on pods running on fargate not Nodegroup

0

Why am I getting Back off restarting failed on AWS-LOAD-BALANCER-CONTROLLER running on Fargate, not Nodegroup? How could this be resolved?

asked a year ago1273 views
2 Answers
0
Accepted Answer

Hello rePost-User-8469491,

While deploying AWS Load Balancer Controller on EKS Fargate, you will have to explicitly specify the VPC ID and Region code as shown in the helm command below. Please refer this RePost article for more info.

helm install aws-load-balancer-controller eks/aws-load-balancer-controller \
    --set clusterName=YOUR_CLUSTER_NAME \
    --set serviceAccount.create=false \
    --set region=YOUR_REGION_CODE \
    --set vpcId=<VPC_ID> \
    --set serviceAccount.name=aws-load-balancer-controller \
    -n kube-system

If you have already done this and still facing issues, check the aws-load-balancer-controller pod logs to find out what is causing the pods to crash.

It would also be helpful if you could share the pod describe output: kubectl describe pod <aws-load-balancer-controller-pod> -n kube-system

Hope this helps!

profile pictureAWS
SUPPORT ENGINEER
answered a year ago
  • aws-load-balancer-controller: Container ID: containerd://*** Image: public.ecr.aws/eks/aws-load-balancer-controller:v2.5.1 Image ID: public.ecr.aws/eks/aws-load-balancer-controller@** Ports: 9443/TCP, 8080/TCP Host Ports: 0/TCP, 0/TCP Args: --cluster-name=Network-EKS-Cluster-V2 --ingress-class=alb --aws-region=us-east-1 State: Waiting Reason: CrashLoopBackOff Last State: Terminated Reason: Error Exit Code: 1 Started: Mon, 01 May 2023 10:01:31 -0600 Finished: Mon, 01 May 2023 10:01:38 -0600 Ready: False Restart Count: 12

  • aws-load-balancer-controller: Container ID: containerd://*** Image: public.ecr.aws/eks/aws-load-balancer-controller:v2.5.1 Image ID: public.ecr.aws/eks/aws-load-balancer-controller@** Ports: 9443/TCP, 8080/TCP Host Ports: 0/TCP, 0/TCP Args: --cluster-name=Network-EKS-Cluster-V2 --ingress-class=alb --aws-region=us-east-1 State: Waiting Reason: CrashLoopBackOff Last State: Terminated Reason: Error Exit Code: 1 Started: Mon, 01 May 2023 10:01:31 -0600 Finished: Mon, 01 May 2023 10:01:38 -0600 Ready: False Restart Count: 12

0

I have removed the taints but the still having CrashLoopBackOff

answered a year ago
  • I used helm to install the load balancer and which i set the vpcid, is there a reason it is not populating the arg?helm install aws-load-balancer-controller eks/aws-load-balancer-controller -n kube-system --set clusterName=Network-EKS-Cluster-V2 --set region=us-east-1 --set vpcid=vpc-* --set serviceAccount.create=false --set serviceAccount.name=aws-load-balancer-controller

  • I used helm to install the load balancer and which i set the vpcid, is there a reason it is not populating the arg?helm install aws-load-balancer-controller eks/aws-load-balancer-controller -n kube-system --set clusterName=Network-EKS-Cluster-V2 --set region=us-east-1 --set vpcid=vpc-* --set serviceAccount.create=false --set serviceAccount.name=aws-load-balancer-controller

  • The command has to be --set vpcId=vpc-abcd. From the above comment, I see that you are passing it as vpcid instead of vpcId. Can you fix that and retry?

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions