You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
antifuchs
changed the title
Any way to retrieve an NLB's listener ARN after reconciliation?
[aws-load-balancer-controller] Any way to retrieve an NLB's listener ARN after reconciliation?
Dec 15, 2022
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
andservice.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).
The text was updated successfully, but these errors were encountered: