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

Hey all, I am facing the exact issue as in this thread: <https://pulumi-community.slack.com/archives/C84L4E3N1/p1582118168389100?thread_ts=1582118168.389100&amp;cid=C84L4E3N1|https://pulumi-community.slack.com/archives/C84L4E3N1/p1582118168389100?thread_ts=1582118168.389100&amp;cid=C84L4E3N1>

Is this resolved or addressed?

Idk how Pulumi engine works, but I think they would need to implement custom-logic to mimic what CloudFormation does to check that the resource is ready. The process is explained in <https://aws.amazon.com/blogs/devops/how-we-sped-up-aws-cloudformation-deployments-with-optimistic-stabilization/|this recent article>.

Is there no other way? All I want to do is to add a ingress rule to the default security group that gets created when the EKS cluster is created so that the node group pods can communicate with internet