ALB INGRESS CONTROLLER STUCK IN PENDING
0
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.
- what could be the issue?
- How can I fix it ?
Tags
Sprache
English
gefragt vor einem Jahr777 Aufrufe
1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
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
beantwortet vor einem Jahr
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 3 Monaten- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
Sounds like you don't have any nodes associated with your cluster. Try kubectl get nodes and past the output here.