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

This looks like the same basic issue as <https://github.com/pulumi/pulumi-kubernetes/issues/1056>

I think the best workaround for now is to poll for the Service similarly to the example in this comment: <https://github.com/pulumi/pulumi-kubernetes/issues/1056#issuecomment-636192266> and then depend on that result instead of using `Service.get`.

I thought we had an issue open for retrying within `.get` calls, but I can’t find it now. I’ll open one to track that, since this is something Pulumi should be able to handle natively.

<https://github.com/pulumi/pulumi-kubernetes/issues/1177>

basically, you are saying I can use custom provider or provisioner to fix my issue (<https://github.com/pulumi/examples/blob/master/aws-ts-ec2-provisioners/provisioners/provisioner.ts>)

I don’t think you necessarily have to do something that heavy. You can put polling logic inside a Promise or Output like in this example: <https://gist.github.com/timmyers/4d2fed53a358d4c98557a5886ae2afbb>