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

I don't fully understand it since the ingress is up and running, but for some reason it fails with the above message.

as a workaround I just skipped the waiting for success part with `skipAwait`

your ingress should expose a service in your cloud provider which updates this field (like an ELB) - which cloud provider are you using?

I'm currently having to use skipAwait as well for traefik (helm install) set as loadbalancer/NLB on EKS.  In production without issue on that front, but never could get the error to go away without skipawait

<@UCWG26BH7>, running k8s on azure with linkerd and traefik. I think it might be a configuration in traefik that is missing so the ingress never gets the status field set.. but this is me guessing. It doesn't seem to impact the ingress though since everything is working.