UpdateSettings control the level of parallelism and the level of
disruption caused during the update of a node pool.
These settings are applicable when the node pool update requires
replacing the existing node pool nodes with the updated ones.
UpdateSettings are optional. When UpdateSettings are not specified
during the node pool creation, a default is chosen based on the
parent cluster's version. For clusters with minor version 1.27 and
later, a default surge_settings configuration with max_surge = 1 and
max_unavailable = 0 is used. For clusters with older versions, node
pool updates use the traditional rolling update mechanism of
updating one node at a time in a "terminate before create" fashion
and update_settings is not applicable.
Set the surge_settings parameter to use the Surge Update mechanism
for the rolling update of node pool nodes.
max_surge controls the number of additional nodes that can be
created beyond the current size of the node pool temporarily for
the time of the update to increase the number of available nodes.
max_unavailable controls the number of nodes that can be
simultaneously unavailable during the update.
(max_surge + max_unavailable) determines the level of parallelism
(i.e., the number of nodes being updated at the same time).
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[],[],null,["# Class UpdateSettings (0.6.21)\n\nVersion latestkeyboard_arrow_down\n\n- [0.6.21 (latest)](/python/docs/reference/gkemulticloud/latest/google.cloud.gke_multicloud_v1.types.UpdateSettings)\n- [0.6.19](/python/docs/reference/gkemulticloud/0.6.19/google.cloud.gke_multicloud_v1.types.UpdateSettings)\n- [0.5.1](/python/docs/reference/gkemulticloud/0.5.1/google.cloud.gke_multicloud_v1.types.UpdateSettings)\n- [0.4.0](/python/docs/reference/gkemulticloud/0.4.0/google.cloud.gke_multicloud_v1.types.UpdateSettings)\n- [0.3.0](/python/docs/reference/gkemulticloud/0.3.0/google.cloud.gke_multicloud_v1.types.UpdateSettings)\n- [0.2.2](/python/docs/reference/gkemulticloud/0.2.2/google.cloud.gke_multicloud_v1.types.UpdateSettings)\n- [0.1.1](/python/docs/reference/gkemulticloud/0.1.1/google.cloud.gke_multicloud_v1.types.UpdateSettings) \n\n UpdateSettings(mapping=None, *, ignore_unknown_fields=False, **kwargs)\n\nUpdateSettings control the level of parallelism and the level of\ndisruption caused during the update of a node pool.\n\nThese settings are applicable when the node pool update requires\nreplacing the existing node pool nodes with the updated ones.\n\nUpdateSettings are optional. When UpdateSettings are not specified\nduring the node pool creation, a default is chosen based on the\nparent cluster's version. For clusters with minor version 1.27 and\nlater, a default surge_settings configuration with max_surge = 1 and\nmax_unavailable = 0 is used. For clusters with older versions, node\npool updates use the traditional rolling update mechanism of\nupdating one node at a time in a \"terminate before create\" fashion\nand update_settings is not applicable.\n\nSet the surge_settings parameter to use the Surge Update mechanism\nfor the rolling update of node pool nodes.\n\n1. max_surge controls the number of additional nodes that can be created beyond the current size of the node pool temporarily for the time of the update to increase the number of available nodes.\n2. max_unavailable controls the number of nodes that can be simultaneously unavailable during the update.\n3. (max_surge + max_unavailable) determines the level of parallelism (i.e., the number of nodes being updated at the same time)."]]
