<p>I have a few questions on EKS node groups.</p>
<ol>
<li><p>I dont understand the concept of Node group and why is it required. Can't we create an EC2 and run kubeadm join for joining EC2 node to EKS Cluster. What advantage does node group hold.</p>
</li>
<li><p>Does node groups (be it managed or self-managed) have to exist in same VPC of EKS cluster. Is it not possible to create node group in another VPC. If so how?</p>
</li>
</ol>

nischeruku
<ol>
<li><a href="https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html" rel="nofollow noreferrer">managed node groups</a> is a way to let AWS manage part of the lifecycle of the Kubernetes nodes. For sure you are allowed to continue to configure <a href="https://docs.aws.amazon.com/eks/latest/userguide/worker.html" rel="nofollow noreferrer">self managed nodes</a> if you need/want to. To be fair you can also spin up a few EC2 instances and configure your own K8s control plane. It boils down to how much you wanted managed Vs how much you want to do yourself. The other extreme on this spectrum would be to use <a href="https://docs.aws.amazon.com/eks/latest/userguide/fargate.html" rel="nofollow noreferrer">Fargate</a> which is a fully managed experience (where there are no nodes to scale, configure, no AMIs etc).</li>
<li>the EKS cluster (control plane) lives in a separate AWS managed account/VPC. See <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-networking.html" rel="nofollow noreferrer">here</a>. When you deploy a cluster EKS will ask you which subnets (and which VPC) you want the EKS cluster to manifest itself (through ENIs that get plugged into your VPC/subnets). That VPC is where your self managed workers, your managed node groups and your Fargate profiles need to be plugged into. You can't use another VPC to add capacity to the cluster.</li>
</ol>
