kubernetes-sigs / kubernetes-sigs/aws-load-balancer-controller
Can't use helm_release terraform resource with public.ecr.aws/eks repo
- Dominant language
- Go
- Stars
- 4.3k
- Forks
- 1.6k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 6
Description
**Bug Description**
when i try to install it with terraform's helm provider like:
```
resource "helm_release" "load_balancer_controller" {
name = "aws-load-balancer-controller"
repository = "oci://public.ecr.aws/eks"
chart = "aws-load-balancer-controller"
version = "v3.2.1"
namespace = "kube-system"
create_namespace = true
...
}
```
terraform drops an error:
```
Unable to locate chart oci://public.ecr.aws/eks/aws-load-balancer-controller:
manifest does not contain minimum number of descriptors (2), descriptors
found: 0
```
**Steps to Reproduce**
Use terraform to install helm chart
**Expected Behavior**
It installs in same way like it can be installed tgz or from `pages`
**Environment**
- AWS Load Balancer controller version: v3.2.1
- Kubernetes version: 1.35
- Using EKS (yes/no), if so version?: EKS 1.35
- Using Service or Ingress: n/a
- AWS region: eu-central-1
- How was the aws-load-balancer-controller installed: n/a, it can't be installed
**Possible Solution (Optional)**
idk what the difference, for example for `karpenter` it works. But i guess karpenter in slightly different repo
Contributor guide
Research direction
Start by reproducing the Terraform helm_release configuration against oci://public.ecr.aws/eks and compare it with a working tgz, pages, or Karpenter repository installation. Investigate why the AWS Load Balancer Controller OCI chart returns no descriptors; done means the chart installs successfully through the shown Terraform configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100