ALB INGRESS CONTROLLER STUCK IN PENDING

Question

I am building an ALB ingress controller for my cluster and it is stuck on pending 0/1. The output of   kubectl get pod (pod name) -n kube-system is  Warning  FailedScheduling  116s  default-scheduler  0/3 nodes are available: 3 Too many pods, 3 node(s) had untolerated taint {eks.amazonaws.com/compute-type: fargate}. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling. 
1) what could be the issue?
2) How can I fix it ?

Answer

It looks like you are configuring ALB Controller on a EKS Fargate only cluster and are trying to deploy to a namespace for which you don't have a Fargate Profile selector. You can find some more details in another post of your's - https://repost.aws/questions/QU8FN4Cq-uQsqA44XbF0pwfA/eks-fargate-one-pod-one-node

--Syd

ALB INGRESS CONTROLLER STUCK IN PENDING

Contenido relevante