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

Untitled.ts

I think line 30 is the bit causing me issues.

so the problem here is that the Kubernetes ingress might have been created (ie, registered in the API server) but the backing load balancer (I'm guessing you're using the AWS load balancer controller?) might not have been provisioned yet

here’s the error `preview` throws, which is understandable. `up` behaves the same way, though:
```  pulumi:pulumi:Stack (demo_env-mattr):
    error: Running program '/Users/matthew.riedel/Source/devex/demo_env' failed with an unhandled exception:
    Error: invocation of aws:lb/getLoadBalancer:getLoadBalancer returned an error: invoking aws:lb/getLoadBalancer:getLoadBalancer: 1 error occurred:
    	* error retrieving LB: LoadBalancerNotFound: Load balancers '[mattr-mattr-lb]' not found
    	status code: 400, request id: 25a5f702-7435-435c-a5a7-ccd7aa948357```

does the ingress resource return a `status` field that gets populated with the load balancer name? if it does, might be able to use an `apply()` on that

I started that way, but maybe I goofed something up.. Let me try again

I don't have a great answer off the top of my head here, but I'll have a crack at this tonight to see if I can find a solution, because I agree this is a problem that we need to try figure out

you might try deploying the ingress manually, inspecting the status output and seeing what's there

Untitled

Here’s what I have now. Will give this a shot.

Just an update on this <@UCWG26BH7> - I tried a few `.apply` approaches (the current one below), and they exhibit the same issue. My hunch is that k8s gets the LB hostname, but AWS hasn’t actually finished creating it yet, so when `getLoadBalancer` is called, it’s not found. I suppose I could wrap the whole thing in some sort of delay, but wondering if there might be a better solution.

FWIW, I decided to use the `ts-retry` module as a workaround. This seems to work for my purposes.

Any drawbacks / idiom-breaking issues with that approach?