Resizing a user cluster

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 managed by the GKE On-Prem API. A user cluster is managed by the GKE On-Prem API if one of the following is true:

• The cluster was created in the Google Cloud console, which automatically configures the GKE On-Prem API to manage the cluster.

• The command gkectl enroll cluster was run on a user cluster, which configures it to be managed by the GKE On-Prem API.

If the GKE On-Prem API is managing a user cluster, use the Google Cloud 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.

Console

1. In the Google Cloud console, go to the GKE Enterprise clusters page.

   Go to the GKE Enterprise clusters page

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 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 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:

   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

Console

1. In the Google Cloud console, go to the GKE Enterprise clusters page.

   Go to the GKE Enterprise clusters page

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 edit Resize.

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

8. Click arrow_back to go back to the previous page.

9. The Google Cloud 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, 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:

kubectl --kubeconfig USER_CLUSTER_KUBECONFIG get nodes

kubectl --kubeconfig USER_CLUSTER_KUBECONFIG describe machinedeployments NODE_POOL_NAME | grep Replicas

Replace the following:

• USER_CLUSTER_KUBECONFIG: the path of the user cluster kubeconfig file

• NODE_POOL_NAME: the name of the node pool that you resized.