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

Can you try using the latest version of the EKS package? v1.0.3 is a tad old. The latest release is v2.2.1, but just about anything after v2.0.0 is fine.

Are you providing both public subnets and private subnets to `subnetIds`?

so the vpc i have only has one subnet a `/16`

Hmm...I'm not sure if that will be an issue or not. Try the newer version of the EKS package, and meanwhile I'll ask internally about using a single subnet.

one thing i should mention it was the ai that generated that old version

still get
```    Cannot assign '{vpcId: string, subnetIds: string, instanceType: string, desiredCapacity: number, minSize: number, maxSize: number, createOidcProvider: boolean, version: string}' to 'eks:index:Cluster':```

I’m still trying to track down if a single subnet will be an issue. Can you try using `publicSubnetIds` (or `privateSubnetIds`, whichever is applicable for your single subnet) instead of `subnetIds`? That’s the approach we use in our YAML template for EKS: <https://github.com/pulumi/templates/tree/master/kubernetes-aws-yaml>