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

Hey everyone,
I’m managing an EKS cluster, but I don’t really understand the diff between the ManagedNodeGroup and NodeGroupV2, which one should we use when creating the EKS cluster an d custom node groups with austoscaling ?

Its... complex.  Stick to ECS is my suggestion.

There are two types of node groups in EKS:
• <https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html|Managed node groups >are backed by an EC2 Auto scaling group that AWS provisions and manages on your behalf. Managed node groups are tagged so that they work with the <https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md|cluster autoscaler> (that you'll have to deploy to the EKS cluster yourself).
• <https://docs.aws.amazon.com/eks/latest/userguide/worker.html|Self-managed nodes> are EC2 instances that you deploy yourself and then add as nodes to the cluster

Unless you have specific requirements, the recommendation is to stick with managed node groups

Thx,
But the NodeGroupV2 is also having an autoscaling config

Yes, the NodeGroupV2 also creates an EC2 Auto scaling group

Thanks, I’m with managed node groups, but I was wondering why in the Guide they were using NodeGroupV2

Not sure which guide you're referring to, do you have a link?

<https://www.pulumi.com/docs/clouds/aws/guides/eks/#configuring-your-eks-clusters-worker-nodes-and-node-groups>

Also, note that placing the EC2 instances in auto scaling groups is a prerequisite for Kubernetes cluster autoscaling but on its own is not sufficient. You need the <https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md|cluster autoscaler> (or use Karpenter for scaling).

Ok, I understand a bit more now the diff between both.

Will stick with managed node groups, but I’m having an issue with LivenessProb / readiness probe and I was wondering if it could be the issue but I think it come from the CNI (I don’t have the addon)

I can’t reach the POD IP from inside the HostNode, I can reach 0.0.0.0:port but not &lt;pod-ip&gt;:port in the same node

&gt; Thanks, I’m with managed node groups, but I was wondering why in the Guide they were using NodeGroupV2
At first glance, I don't see why the tutorial would not work with a managed node group.

&gt; I’m having an issue with LivenessProb / readiness probe and I was wondering if it could be the issue but I think it come from the CNI (I don’t have the addon)
&gt; 
&gt; I can’t reach the POD IP from inside the HostNode, I can reach 0.0.0.0:port but not &lt;pod-ip&gt;:port in the same node
This sounds like a Kubernetes networking problem that's unrelated to the Pulumi resource or the flavor of node group you deploy.

Maybe <https://aws.github.io/aws-eks-best-practices/networking/vpc-cni/> is a good start.

Yes, but this is weird that following the GUIDE I’m having this issue without touching anything else

Didn't you say that you don't use the Amazon VPC CNI plugin?

I just never Installed the ADDON for now, but it look like I’m using it I can see it in the aws-node daemonset

I did the awsx VPC and eks Cluster + node groups nothing else.

I will keep you up to date I’m deploying other apps to see if this is specific to an app, because I have argocd / nginx and they are working fine

cert manager etc