Reputation: 103
I am trying to deploy the aws-load-balancer-controller on my Kubernetes cluster on AWS = by following the steps given in https://docs.aws.amazon.com/eks/latest/userguide/aws-load-balancer-controller.html
After the yaml file is applied and while trying to check the status of the deployment , I get :
$ 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 6m39s
I tried to debug it and I got this :
$ kubectl logs -n kube-system deployment.apps/aws-load-balancer-controller
{"level":"info","logger":"controller-runtime.metrics","msg":"metrics server is starting to listen","addr":":8080"}
{"level":"error","logger":"setup","msg":"unable to create controller","controller":"Ingress","error":"the server could not find the requested resource"}
The yaml file is pulled directly from https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.3.0/v2_3_0_full.yaml and apart from changing the Kubernetes cluster name, no other modifications are done.
Please let me know if I am missing some step in the configuration. Any help would be highly appreciated.
Upvotes: 9
Views: 5672
Reputation: 1679
As has been pointed by Gearheads' answer, issues of this type occur mostly due to version mismatches i.e. EKS version and AWS Load Balancer Controller version.
The good news, however, is that for almost all practical cases the AWS Load Balancer Controller comes with backward compatibility and thus installing the latest version as explained in this AWS doc should solve the issue as it did for me!
Upvotes: 0
Reputation: 131
I am not sure if this helps, but for me the issue was that the version of the aws-load-balancer-controller was not compatible with the version of Kubernetes.
Github issue for more information: https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/2495
Upvotes: 10