Delete a node pool
Stay organized with collections
Save and categorize content based on your preferences.
This page shows you how to delete node pools in GKE on AWS.
Before you begin
This page assumes you are familiar with the cluster autoscaler. For more information, see Cluster autoscaler.
Delete a node pool
To delete a node pool, run the following command:
Console
In the Google Cloud console, go to the Google Kubernetes Engine clusters overview page.
Select the Google Cloud project that the cluster is in.
In the cluster list, select the name of the cluster, and then select View details in the side panel.
Select the Nodes tab to see a list of all the node pools.
Select a node pool from the list.
Near the top of the window, click Delete.
If the delete fails, follow the steps in the
gcloudtab and add the--ignore-errorsflag to thegcloud container aws node-pools deletecommand.
gcloud
Get a list of your node pools:
gcloudcontainerawsnode-poolslist\ --clusterCLUSTER_NAME\ --locationGOOGLE_CLOUD_LOCATIONReplace the following:
CLUSTER_NAME: the name of the cluster that the node pool is attached toGOOGLE_CLOUD_LOCATION: the Google Cloud location hosting the node pool
For each of your node pools, delete it with the following command:
gcloudcontainerawsnode-poolsdeleteNODE_POOL_NAME\ --clusterCLUSTER_NAME\ --locationGOOGLE_CLOUD_LOCATIONReplace the following:
NODE_POOL_NAME: the name of the node pool to deleteCLUSTER_NAMEGOOGLE_CLOUD_LOCATION
If the command returns an error and the delete fails, you can force the deletion by running the command again with the
--ignore-errorsflag. This flag is available in version 1.29 and later.
How GKE on AWS protects workloads during node pool deletion
During node pool deletion, GKE on AWS performs graceful shut down on each node without honoring PodDisruptionBudget. It takes the following steps:
- Disable cluster autoscaler if it was enabled.
- Set up a deadline for the draining process. After this deadline, even if there are still Pod objects existing, GKE on AWS stops draining and proceeds to deleting underlying virtual machines. The default deadline is 5 minutes. For every 10 more nodes, 5 more minutes is added.
- Cordon all the nodes in the node pool.
- Before deadline is met, delete Pod objects in the node pool with best efforts.
- Delete all the underlying compute resources.
What's next
- Read the reference guide for gcloud container aws node-pools .