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).
Protobuf type google.cloud.gkemulticloud.v1.UpdateSettings
[[["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 2026-02-27 UTC."],[],[]]
