To make basic configuration changes to the deployed Google Kubernetes Engine (GKE) resources, it is recommended that you edit and redeploy the blueprint.
Limitations
The following changes can't be made by editing the blueprint:
- You can't switch from a zonal to a regional GKE cluster. To switch from a zonal to a regional cluster, you must create a new cluster.
- You can't update the GKE version by using the Cluster Toolkit. To update the GKE version, you must change the version using the Google Cloud console or Google Cloud CLI.
- You can't resize a Parallelstore file system in-place. Attempting to resize by editing the blueprint results in the Parallelstore file system being destroyed and re-created.
Reconfigure the cluster
For GKE clusters, you can update the cluster as follows:
- Edit the deployment blueprint to update the supported parameters. For a list of supported parameters, see Supported parameters.
- Run the
./gcluster deploy <blueprint-yaml-file> -wcommand to redeploy the environment.
Supported parameters
When you update the blueprint, the following parameters can be modified.
| Parameters | Description |
|---|---|
autoscaling_total_min_nodes and autoscaling_total_max_nodes in a nodepool |
Use this parameter to update the minimum and maximum number of nodes that exist within an autoscaling nodepool. |
static_node_count in a nodepool |
Use this parameter to adjust the static number of nodes in the nodepool. You can also replace this parameter with autoscaling_total_min_nodes and autoscaling_total_max_nodes to switch your cluster from a static to an autocale nodepool. |
disk_size_gb in a nodepool |
Use this parameter to adjust the size of the disk attached to each node to meet your workload requirements. |