<p>We're trying to set up a spot node group in EKS with lower and higher capacity instance types, (e.g. <code>instance_types = [&quot;t3.xlarge&quot;, &quot;c5.4xlarge&quot;]</code>), but ... only the t3 is used, even if we specify more CPU than it has to offer. Pods still try to use it and just hang.</p>
<p>How do we get the larger instances to come into play?</p>

<p>An AWS AutoScalingGroup has the ability to put weights on the instance types, but that functionality isn't built into EKS. So what's happening is that the ASG is designed to create the first instance type if possible, and doesn't get impacted by your K8s workload requests, and therefor will always be the first type that is available.</p>
<p>You probably want to <strong>create two different node groups</strong> (one for the <code>t3.xlarge</code> and another for the <code>c5.4xlarge</code>). And depending on the workloads, maybe allow the min-size to be 0.</p>
<p>Alternatively, if you want to explicitly change the existing node group and not have two, then maybe these instructions would be useful: <a href="https://blog.porter.run/updating-eks-instance-type/" rel="nofollow noreferrer">https://blog.porter.run/updating-eks-instance-type/</a></p>
