This message was deleted.

sparse-intern-71089

06/03/2019, 5:32 PM

This message was deleted.

white-balloon-205

06/03/2019, 5:36 PM

This has come up before - and as far as I can tell Kubernetes does not provide any way to retrieve this. If others have figured out how to do it - I'd love to hear.

creamy-potato-29402

06/03/2019, 8:06 PM

No, and this is a platform choice from AWS, which could provide a custom controller for htis.

shy-receptionist-99213

06/03/2019, 10:23 PM

i’ve just checked one

LoadBalancer

svc in our cluster, and you should be able to get lb dns record from

status.loadBalancer.ingress[0].hostname

shy-receptionist-99213

06/03/2019, 10:23 PM

not sure if this field is accessible in pulumi though

shy-receptionist-99213

06/03/2019, 10:27 PM

https://kubernetes.io/docs/concepts/services-networking/#loadbalancer

creamy-potato-29402

06/03/2019, 10:49 PM

the file?

shy-receptionist-99213

06/03/2019, 10:56 PM

Sorry, typo, I meant

field

white-balloon-205

06/03/2019, 11:11 PM

Ahh - yes - if I recall correctly the problem is that AWS does not offer any API to lookup LoadBalancer's by hostname, so although you know the hostname, the only way to get back the identity of the loadbalancer would be to list all loadbalancers and filter down. That's possible, but somewhat involved. What Kubernetes should do is record the ARN or

name

of the loadbalancer so that it can be looked up.

creamy-potato-29402

06/03/2019, 11:12 PM

yes, that’s right.

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.