Resizing a user cluster means adding or removing nodes. Adding nodes
requires that IP addresses are available for the new nodes. You resize a user
cluster by changing the number of replicas in the node pool.

For information on maximum and minimum limits for user clusters, see
[Scalability limits](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/concepts/scalability.md.txt#limits).

For information on managing node pools, see
[creating and managing node pools](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/how-to/managing-node-pools.md.txt).

## Verify that enough IP addresses are available

If you intend to have N nodes after the resizing, then you must have N + 1 IP
addresses available.

Before resizing a cluster, verify that you have enough IP addresses. How you do
the verification depends on whether the cluster uses a DHCP server or static IP
addresses.

### DHCP

If the cluster uses DHCP, check that the DHCP server can provide enough IP
addresses. It must be able to provide at least one more IP address than the
number of nodes that will be in the cluster after the resizing.

### Static IPs

How you verify that you have enough static IP addresses depends on whether the
cluster is enrolled in the GKE On-Prem API. A user cluster is enrolled in
the GKE On-Prem API if one of the following is true:

- The cluster was created by using the Google Cloud console, the Google Cloud CLI
  (gcloud CLI), or Terraform, which automatically enrolls the
  cluster in the GKE On-Prem API. Collectively, these standard applications are
  referred to as GKE On-Prem API clients.

- The command `gkectl enroll cluster` was run on a user cluster, which
  [configures it to be managed by the GKE On-Prem API](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/how-to/enroll-cluster.md.txt).

If the GKE On-Prem API is managing a user cluster, use the
console to count the number of IPs and add more IPs if needed.
If the user cluster isn't managed by the GKE On-Prem API, you can run
`gkectl update cluster` first, which verifies whether you've allocated enough
IP addresses in the cluster. If not, you can find the number of extra IP
addresses needed in the error message.

## Add static IPs

If the cluster is managed by the GKE On-Prem API, use the
console to add more IP addresses. Otherwise, use the command
line on your admin workstation.

### Console

1. In the console, go to the **Google Kubernetes Engine clusters overview**
   page.

   [Go to GKE clusters](https://console.cloud.google.com/kubernetes/list/overview)
2. Select the Google Cloud project that the user cluster is in.

3. In the cluster list, click the name of the cluster, and then click
   **More details** in the **Details** panel.

4. In the **Networking** section, click **Edit**.

5. In the **Add additional static IP addresses** dialog box, click
   **Add IP Address** . Enter the IP address and optionally, a hostname.
   Repeat as needed. When finished, click **Done**.

### Command line

1. Open the user cluster's [IP block file](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/how-to/ip-block-file.md.txt)
   for editing.

2. Verify that all of the IP addresses you intend to use for the user cluster
   are included in the IP block file. The IP block file should have at least
   one more IP address than the number of nodes that will be in the cluster
   after the resizing.

3. To view the addresses reserved for a user cluster:

   ```bash
   kubectl get cluster --kubeconfig ADMIN_CLUSTER_KUBECONFIG \
     --namespace USER_CLUSTER_NAME USER_CLUSTER_NAME --output yaml
   ```

   Replace the following:
   - `ADMIN_CLUSTER_KUBECONFIG`: the path of the admin cluster kubeconfig file
   - `USER_CLUSTER_NAME`: the name of the user cluster
4. Add as many additional static IP addresses to the corresponding block as required, and then
   run `gkectl update cluster`.

Here is an example of an IP block file that has four IP addresses and the
corresponding hostnames:

```
hostconfig:
dns: 172.16.255.1
tod: 216.239.35.0
blocks:
- netmask: 255.255.248.0
  gateway: 21.0.135.254
  ips:
  - ip: 21.0.133.41
    hostname: user-node-1
  - ip: 21.0.133.50
    hostname: user-node-2
  - ip: 21.0.133.56
    hostname: user-node-3
  - ip: 21.0.133.47
    hostname: user-node-4
```

## Resize the cluster

### Console

1. In the console, go to the **Google Kubernetes Engine clusters overview**
   page.

   [Go to GKE clusters](https://console.cloud.google.com/kubernetes/list/overview)
2. Select the Google Cloud project that the user cluster is in.

3. In the cluster list, click the name of the cluster, and then click
   **More details** in the **Details** panel.

4. Click the **Nodes** tab.

5. Click the name of the node pool that you want to resize.

6. Click **Resize**.

7. In the **Nodes** field, enter the number of nodes that you want in
   the node pool, and then click **Done**.

8. Click to go back to the
   previous page.

9. The console displays **Cluster status: changes in
   progress** . Click **Show Details** to view the **Resource status
   condition** and **Status messages**.

### Command line

In the
[user cluster configuration file](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/how-to/user-cluster-configuration-file-latest.md.txt#nodepool-replicas-field),
update the value of the `replicas` field in one or more of the `nodePools`
elements.

Resize the cluster:

```
gkectl update cluster --kubeconfig ADMIN_CLUSTER_KUBECONFIG --config USER_CLUSTER_CONFIG
```

Replace the following:

- `ADMIN_CLUSTER_KUBECONFIG`: the path of the admin cluster kubeconfig file

- `USER_CLUSTER_CONFIG`: the path of the user cluster configuration file

Verify that the resizing succeeded:

- If [advanced cluster](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/how-to/admin-cluster-configuration-file-latest.md.txt#enable-advanced-cluster-field) isn't enabled:

  ```bash
  kubectl --kubeconfig USER_CLUSTER_KUBECONFIG get nodes

  kubectl --kubeconfig USER_CLUSTER_KUBECONFIG describe machinedeployments NODE_POOL_NAME | grep Replicas
  ```
- If [advanced cluster](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/how-to/admin-cluster-configuration-file-latest.md.txt#enable-advanced-cluster-field) is enabled

  ```bash
  kubectl --kubeconfig USER_CLUSTER_KUBECONFIG get nodes

  kubectl --kubeconfig ADMIN_CLUSTER_KUBECONFIG describe nodepoolclaim -n USER_CLUSTER_NAMESPACE NODE_POOL_NAME | grep "Node Count"
  ```

Replace the following:

- `ADMIN_CLUSTER_KUBECONFIG`: the path of the admin cluster
  kubeconfig file

- `USER_CLUSTER_KUBECONFIG`: the path of the user cluster
  kubeconfig file

- `NODE_POOL_NAME`: the name of the node pool that you
  resized.

- `USER_CLUSTER_NAMESPACE`: the namespace of the user cluster that you
  resized.

## Troubleshooting

See
[Troubleshooting cluster creation and upgrade](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/troubleshooting/create-upgrade.md.txt).