Failing CloudInit and Kubelet setup during worker node startup about pulumi-eks HOT 2 CLOSED

We dug into this offline. It turns out that the root cause here is that some worker nodes were being created in public subnets and had no route to the EKS API server. This was because the subnetIds argument to the eks.Cluster contained both public and private subnets, and this list is passed verbatim to the CF template that boots the worker nodes. I am investigating whether or not eks.Cluster can and should automatically filter out these public subnets or whether we ought to expose an additional argument s.t. the user can restrict the subnets in which workers are created.

from pulumi-eks.

This was due to incorrect EKS networking setup. Had workers deploying to public subnets. Fix is to only put workers on the private subnets.

from pulumi-eks.