AWS load balancer not getting provisioned on installing controller in AWS EKS
- Dominant language
- Mustache
- Stars
- 1.3k
- Forks
- 1.1k
- Avg merge
- 22m
- Merged PRs (30d)
- 5
Description
**Describe the bug**
On installation of latest version of aws-load-balancer-controller from `https://github.com/aws/eks-charts/tree/master/stable/aws-load-balancer-controller` on AWS EKS 1.24, the load balancer is not getting provisioned in AWS console.
**Steps to reproduce**
1. Deploy a AWS EKS cluster of version 1.24.
2. Install aws-load-balancer controller on EKS cluster using below command:
`helm upgrade --install aws-load-balancer-controller ~/eks_charts/stable/aws-load-balancer-controller --set clusterName={cluster-name} -n kube-system --debug`
**Expected outcome**
Previously we were using AWS EKS 1.21 with aws-load-balancer-controller v2.1.3. During installation of controller, the AWS Application Load Balancer got provisioned in the same region where EKS was deployed. But during installion of conroller(v2.4.5) in EKS 1.24, it is not provisioning the load balancer.
**Environment**
AWS EKS
* Chart name: eks-charts
* Chart version: 1.4.6
* Kubernetes version: v1.24.7-eks-fb459a0 (Client Version)
* Kustomize Version: v4.5.4
* Using EKS (yes/no), if so version? yes(1.24)
**Additional Context**:
Attaching the difference in logs while installing controller in previous environment(EKS 1.21 with 2.1.3 controller) vs new environment(EKS 1.24 with 2.4.5 controller)
Please help us resolve this issue.
[Logs.pdf](https://github.com/aws/eks-charts/files/10391419/Logs.pdf)
Contributor guide
Research direction
Start with the Helm installation command and the attached Logs.pdf, comparing the EKS 1.21/controller v2.1.3 environment with EKS 1.24/controller v2.4.5. Reproduce the installation on EKS 1.24 using chart version 1.4.6 and inspect why the controller does not provision a load balancer. Done means the controller installation provisions the AWS load balancer in the EKS region.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100