[aws-load-balancer-controller] Any way to retrieve an NLB's listener ARN after reconciliation?
- Dominant language
- Mustache
- Stars
- 1.3k
- Forks
- 1.1k
- Avg merge
- 22m
- Merged PRs (30d)
- 5
Description
**Is your feature request related to a problem?**
We're trying to set up AWS PrivateLink "endpoint services" for various services in our k8s cluster, and are using aws-load-balancer-controller to manage the NLBs for each of these services - we create a Service object and awf-lb-c reconciles & creates the NLB for us. Unfortunately, the only information we get out of the controller at this point is the load balancer hostname, on the Service status object.
At that point, we pretty much have to poll and find the NLB matching either the hostname on the status, or repeatedly try and find the NLB via the `elbv2.k8s.aws/cluster` and `service.k8s.aws/stack` tags. Neither is really satisfying.
**Is your feature request related to a specific Helm chart, if yes mention name of the chart?**
no
**Describe the solution you'd like**
Ideally, aws-load-balancer-controller could attach more data to the Service object describing the concrete details of the NLB created, or keep track of these linkages in a separate CRD, so other controllers could watch for these.
**Describe alternatives you've considered**
(see above for what we do; it's kinda bad).
Contributor guide
Research direction
Start with the aws-load-balancer-controller reconciliation of a Kubernetes Service object and how the created NLB is represented in Service status. Compare the requested listener ARN and linkage information with the current hostname-only output, then define what data other controllers should be able to watch and what successful reconciliation should expose.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100