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

That is very surprising. There should be no direct relationship between the kubernetes version used and the NodeGroup constructed by the EKS package. 

Can you share any more details on your code and/or the preview/update output you see?

Luke, is it OK to give our stack log link in your direct chat?

<@UB3BGTV63> is it OK to give our stack log link in your direct chat?

<@UB3BGTV63> I think we found the problem with version 1.16.  it is kind of not honoring the dependency .

In the code, we specify eks cluster, specify node group   and specify helm charts.   we already have specified helm charts depend on eks cluster creation. When we started new stack with 1.16, helm charts were failing and timing out after X seconds because of apiVersion issues which is not allowing to create node group(ec2). We think creation of resources go in parallel unless we specify the dependency.
When I added node group as dependency for helm charts, it started seeing the creation of ec2 and was able to identify the errors in helm charts and resolve them.