Help improve this page
Want to contribute to this user guide? Scroll to the bottom of this page and select Edit this page on GitHub. Your contributions will help make our user guide better for everyone.
Delete a managed node group from your cluster
This topic describes how you can delete an Amazon EKS managed node group. When you delete a managed node group, Amazon EKS first sets the minimum, maximum, and desired size of your Auto Scaling group to zero. This then causes your node group to scale down.
Before each instance is terminated, Amazon EKS sends a signal to drain the Pods from that node. If the Pods haven't drained after a few minutes, Amazon EKS lets Auto Scaling continue the termination of the instance. After every instance is terminated, the Auto Scaling group is deleted.
Important
If you delete a managed node group that uses a node IAM role that isn't used by any
other managed node group in the cluster, the role is removed from the
aws-auth
ConfigMap
. If any of the self-managed node groups in the cluster are
using the same node IAM role, the self-managed nodes move to the NotReady
status. Additionally, the cluster operation is also disrupted.
To add a mapping for
the role you're using only for the self-managed node groups, see Create access entries, if your cluster's platform version is at least
minimum version listed in the prerequisites section of Grant IAM users access to Kubernetes with EKS access entries.
If your platform version is earlier than the required minimum version for access entries, you can add the
entry back to the aws-auth
ConfigMap
. For more information, enter eksctl create
iamidentitymapping --help
in your terminal.
You can delete a managed node group with eksctl
or the AWS Management Console.