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.

Pulumi Community

the helm chart likely creates a Kubernetes svc of type `LoadBalancer` which you can query, which will return the lb name

however, you’re not going to be able to fully manage this unless you create it yourself

what exactly are you trying to do? there are Kubernetes annotations you can specify which will allow you to do most things you want to do with the LB

I’m wanting to apply the right listeners on the LB. So maybe the approach would be to create the LB in Pulumi and then tell the istion-ingressgateway to use that when installed from the chart resource?

I was also thinking of creating a dynamic resource that uses boto3 to get the LB (using depends_on istio-ingressgateway chart resource so I could enforce ordering) and importing it, though I don’t know how well that would work in practice.