aws / aws/eks-charts

AWS load balancer controller CDR update fails from master

Open
#1,286 1 comment 16 reactions 0 assignees View on GitHub
bug
Dominant language
Mustache
Stars
1.3k
Forks
1.1k
Avg merge
22m
Merged PRs (30d)
5

Description

**Describe the bug**
I am trying to update CRDs from master using terraform. But it results in following error.
```
Executing: ["/bin/sh" "-c" "KUBECONFIG=/tmp/.tmp-kube-saas_sbx_apse2_reno/config kubectl apply -k \"github.com/aws/eks-charts/stable/aws-load-balancer-controller/crds?ref=master\" --validate=false"]

[2025-12-22T00:56:09.903Z] null_resource.alb-ingress-controller-crd (local-exec): error: accumulating resources: accumulation err='merging resources from 'aga-crds.yaml': may not add resource with an already registered id: CustomResourceDefinition.v1.apiextensions.k8s.io/globalaccelerators.aga.k8s.aws.[noNs]': must build at directory: '/tmp/kustomize-3453331283/stable/aws-load-balancer-controller/crds/aga-crds.yaml': file is not directory
```

**Steps to reproduce**
Run CRD update on existing deployment
kubectl apply -k \"github.com/aws/eks-charts/stable/aws-load-balancer-controller/crds?ref=master\"
**Expected outcome**
Successful CRD update
**Environment**
EKS
* Chart name:
* Chart version:
* Kubernetes version:1.33
* Using EKS (yes/no), if so version?yes

Contributor guide

Open the contributing guide

Research direction

Start with stable/aws-load-balancer-controller/crds/aga-crds.yaml and the other CRD manifests referenced by the kustomize command. Reproduce the kubectl apply -k command against the master ref, identify the duplicate globalaccelerators.aga.k8s.aws resource, and verify that an existing deployment can update its CRDs successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes, terraform
Domain
cloud, devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.