the k8s API is publicly accessible in EKS. so the workers can correctly initiate a process to join the cluster. EKS already has multiple distinct subnets for workers in its different regions. my understanding is that as long as the control plane and the worker are reachable to each other, in this case over netmaker provisioned on the windows host, the node will be Ready