Gordon McAllister

I notice @andrescaroc's `NodePool` excludes them, however on our clusters (see my colleague @marcofranssen's [comment](https://github.com/aws/karpenter-provider-aws/issues/7029#issuecomment-2653128622) for specifics but we are on latest Karpenter/EKS/Bottlerocket versions) I can reproduce this on arm64...

@Shreyank031 thanks for the suggestion, as mentioned upthread we use Bottlerocket nodes exclusively and had previously tried setting `spec.kubelet.systemReserved` fields. I set them to match your values, however still encountered...

Following up: Our workaround is to follow the same [requirements](https://docs.aws.amazon.com/eks/latest/userguide/automode-learn-instances.html#auto-supported-instances) for minimum node size used by EKS Auto Mode. So our NodePool requirements now include: ```yaml - key: karpenter.k8s.aws/instance-cpu operator:...