[Feature] aws-load-balancer-controller addon

[pbarker]

What feature/behavior/change do you want?

A simple was to add aws-load-balancer-controller to a cluster

Why do you want this feature?

Because most clusters need ingress and its still very cumbersome to do so

[github-actions[bot]]

Hello pbarker :wave: Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website

[cPu1]

AWS Load Balancer Controller is not available as an EKS addon yet. We do not have any plans to support self-managed versions of addons. You can track this issue for more details.

[skubot]

@pbarker It's quite easy to setup AWSLoadBalancerController... in your cluster.yaml add...

iam:
  podIdentityAssociations:
    - namespace: kube-system
      serviceAccountName: aws-load-balancer-controller
      createServiceAccount: true
      wellKnownPolicies:
        awsLoadBalancerController: true
addons:
  - name: eks-pod-identity-agent
  - name: vpc-cni
    podIdentityAssociations:
      - namespace: kube-system
        serviceAccountName: aws-node
        permissionPolicyARNs: ['arn:aws:iam::aws:policy/AmazonEKS_CNI_Policy']

then using helm...

helm repo update eks

helm install aws-load-balancer-controller eks/aws-load-balancer-controller \
  -n kube-system \
  --set clusterName=${CLUSTER_NAME} \
  --set region=us-west-2 \
  --set serviceAccount.create=false \
  --set serviceAccount.name=aws-load-balancer-controller

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 5 days with no activity.