Resizing a Cluster

This page explains how to resize container clusters. You can resize a container cluster to increase or decrease the number of nodes in that cluster.

Before you begin

To prepare for this task, perform the following steps:

• Ensure that you have installed the Cloud SDK.
• Set your default project ID:

  gcloud config set project [PROJECT_ID]

• Set your default compute zone:

  gcloud config set compute/zone [COMPUTE_ZONE]

• Update all gcloud commands to the latest version:

  gcloud components update

Note: You can override these default settings in gcloud commands using the --project and --zone operational flags.

Resizing a cluster

Console

To resize your cluster's node pools, perform the following steps:

1. Visit the Kubernetes Engine menu in GCP Console.

   Visit the Kubernetes Engine menu

2. Select the desired cluster.

3. Click Edit.
4. From the Node pools menu, change the value of the Current size field to the desired value. Repeat for each node pool as needed.
5. Click Save.

gcloud

To resize your cluster's node pools, you use the gcloud container clusters resize command. You must specify the cluster's name, the name of the desired node pool, and the new number of nodes:

gcloud container clusters resize [CLUSTER_NAME] --node-pool [NODE_POOL] \
    --size [SIZE]

Repeat this command for each node pool. If your cluster only has its default node pool, omit the --node-pool flag.

For more information, refer to the gcloud container clusters resize documentation.

Increasing the size of your cluster

When you increase the size of a cluster:

• New node instances are created using the same configuration as the existing instances
• New Pods may be scheduled onto the new instances
• Existing Pods are not moved onto the new instances

When you increase the size of a node pool that spans multiple zones, the new size represents the number of nodes in the node pool per zone. For example, if you have a node pool of size 2 spanning two zones, the total node count is 4. If you resize the node pool to size 4, the total node count becomes 8.

Decreasing the size of your cluster

When you decrease the size of a cluster:

• The Pods that are scheduled on the instances being removed are killed
• Pods managed by a replication controller are rescheduled by the controller onto the remaining instances
• Pods not managed by a replication controller are not restarted

The managed instance group does not differentiate between instances running Pods and instances without Pods. Resizing down removes instances at random.

Decreasing the size of your cluster with drain

Beta

This is a Beta release of cluster resize with drain. This feature is not covered by any SLA or deprecation policy and might be subject to backward-incompatible changes.

You can manually decrease the size of your cluster and have such instance's Pods be drained before they are removed.

Note: To use gcloud beta commands, you must configure gcloud to use the v1beta1 API.

Warning: Do not use both Cluster Autoscaler and manual resize commands simultaneously on a node pool, as this can cause interactions that result in unstable and/or incorrect node pool size.

To decrease and drain your cluster, run the following command:

gcloud beta container clusters resize [CLUSTER_NAME] --node-pool [NODE_POOL] \
--size [SIZE]

Autoscaling a cluster

Kubernetes Engine's cluster autoscaler feature automatically resizes your node pools in response to changing conditions, such as changes in your workloads and resource usage.

To learn more about how autoscaling works, refer to the Cluster Autoscaler documentation.

What's next

• Learn more about clusters.