title: AWS Load Balancer Failed to Deploy
body: <p>I'm trying to create AWS ALB-Ingress through EKS following the steps in the document <a href="https://docs.aws.amazon.com/eks/latest/userguide/alb-ingress.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/eks/latest/userguide/alb-ingress.html</a></p>
  <p>I was successful till the step 7 in creating the controller:</p>
  <pre><code>[ec2-user@ip-X-X-X-X eks-cluster]$ kubectl apply -f v2_0_0_full.yaml 
  customresourcedefinition.apiextensions.k8s.io/targetgroupbindings.elbv2.k8s.aws created 
  mutatingwebhookconfiguration.admissionregistration.k8s.io/aws-load-balancer-webhook created 
  Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply 
  serviceaccount/aws-load-balancer-controller configured 
  role.rbac.authorization.k8s.io/aws-load-balancer-controller-leader-election-role created 
  clusterrole.rbac.authorization.k8s.io/aws-load-balancer-controller-role created 
  rolebinding.rbac.authorization.k8s.io/aws-load-balancer-controller-leader-election-rolebinding created 
  clusterrolebinding.rbac.authorization.k8s.io/aws-load-balancer-controller-rolebinding created 
  service/aws-load-balancer-webhook-service created 
  deployment.apps/aws-load-balancer-controller created 
  certificate.cert-manager.io/aws-load-balancer-serving-cert created 
  issuer.cert-manager.io/aws-load-balancer-selfsigned-issuer created 
  validatingwebhookconfiguration.admissionregistration.k8s.io/aws-load-balancer-webhook created
  </code></pre>
  <p>However, the controller does NOT get to &quot;Ready&quot; status:</p>
  <pre><code>[ec2-user@ip-X-X-X-X eks-cluster]$ kubectl get deployment -n kube-system aws-load-balancer-controller
  NAME                           READY   UP-TO-DATE   AVAILABLE   AGE
  aws-load-balancer-controller   0/1     1            0           29m
  
  </code></pre>
  <p>I'm also able to list the pod associated with the controller which also shows NOT READY:</p>
  <pre><code>[ec2-user@ip-X-X-X-X eks-cluster]$ kubectl get pods -n kube-system
  NAME                                            READY   STATUS    RESTARTS   AGE
  aws-load-balancer-controller-XXXXXXXXXX-p4l7f   0/1     Pending   0          30m
  </code></pre>
  <p>I also can't seem to get its logs in order to try and debug the issue:</p>
  <pre><code>[ec2-user@ip-X-X-X-X eks-cluster]$ kubectl -n kube-system logs aws-load-balancer-controller-XXXXXXXXXX-p4l7f
  [ec2-user@ip-X-X-X-X eks-cluster]$
  </code></pre>
  <p>Furthermore, the /var/log directory also does not have any related logs.</p>
  <p>Please help me understand why it is not coming to READY state. Also let me know how to enable logging to debug these kind of issues.</p>