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 believe it is all related because the spec path changes from `serviceName` to `service.name` in the newer api.

and i'm also seeing
```No matching service found for ingress rule: "<http://topsecret.stage.myrootdomain.net|topsecret.stage.myrootdomain.net>" -&gt; ""```
which leads me to believe it's getting undefined trying to access the incorrect property.

we recently bumped our kube api in eks from 1.14 --&gt; 1.19 so I know this has some deprecated and removed API things as well. however, I wouldn't think deprecated would mean not working.

the helm chart ingress is also `apiVersion: extensions/v1beta1` so I really have no idea where pulumi is deciding oh wait a second this is the new api

it just hangs
````  No matching service found for ingress rule:```
but it's not true. the service is found and the ingress even works

I had the same thing. ingress worked but the console was complaining and hanging.
Changing the definition from the v1beta to this, worked fine.
```new k8s.networking.v1.Ingress(...)```

damn, glad to know... sadly i'm using a helm chart and isn't the new version. I'll try a transformation.

definitely something strange in the ingress await logic. can't figure out what. <https://github.com/pulumi/pulumi-kubernetes/blob/536b37bb61cc6f9d6a041748ad96a575aebeef44/provider/pkg/await/ingress.go> . Somewhere around
```checkIfEndpointsReady``` Even tried SkipAwait:true annotation and it didn't help```