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

*`kubernetes.networking.v1.Ingress`* appears to <https://www.pulumi.com/registry/packages/kubernetes/api-docs/networking/v1/ingress/#ingress|expect a LB address> to populate in status before accepting the resource as being healthy? I'm not seeing an opt-out for this which is causing difficulty behind noteport / hostport type ingress controllers.

Am I missing something, or should I be trying to accomplish this another way?

You can add an annotation:

`<http://pulumi.com/skipAwait=true|pulumi.com/skipAwait=true>`

Works on any Kubernetes resource that has await logic :slightly_smiling_face:

This with KIC <@U029HQAKWQ0>? There's an option to populate that field from KIC for this scenario.

<@U02F9P6KGD7> I was going to look into that soon, havent come across it.

Ref?

`publish_status_address` in the helm chart, I set it to whatever my external ingress host it `<http://testexample.com|testexample.com>` or whatever.

not really functionally used I don't think (because we take care of all the listening / routing with kong), but satisfies the above check.