This message was deleted.

also found these github issues: https://github.com/pulumi/pulumi-kubernetes/issues/1537 https://github.com/pulumi/pulumi-kubernetes/issues/1498 https://github.com/pulumi/pulumi-kubernetes/issues/1649 That seem to be related

I know what this is, just read it yesterday in a blog, let me find it

Been looking at this for a while but I still can't make it work. seems like something doesn't meet the conditions. Also, this would put the POD into a "not ready" state until it gets registered to the ALB. In my case, the ALB is in provisioning state (i'm creating it as well). I still think this is a pulumi error on the awaits. I found another older github issue where the problem was the same for

extensions/v1beta1

I have the same issue too. In fact in my case, the issue is not related to the POD readiness at all. everything works except the status.loadBalancer.ingress[0].ip or hostname both return empty at all times

I ended up working around this issue because pulumi team did not yet update the logic behind the await for the ingress. The next version of kubernetes will deprecate the extensions.v1beta.ingress (which is the one that works). I found out that you could technically use an ingress of type

extensions.v1beta.ingress

but it is alreadt marked as deprecated. In my case, I was using

aws-load-balancer-controller

and I switched to

traefik

using custom resource definition for

ingressRoute

which works around the issue of creating and awaiting ingress resources. https://doc.traefik.io/traefik/v2.2/providers/kubernetes-crd/ @dry-sugar-63293