Update Node Pool

gke.update_node_pool
ActionGoogle Cloudconnection required

Calls GKE API v1 PUT .../clusters/{c}/nodePools/{np}.

Update a node pool — its node version, image type, tags, labels, taints or upgrade settings. This is what upgrades the nodes.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Kubernetes Engine
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id, location
Resolved by
config.connection_id, else node.connection_id

Configuration

5 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
location
Zone or region of the cluster (overrides connection).
stringNo———
cluster
Cluster name.
stringYes———
node_pool
Node pool name.
stringYes———
update
An UpdateNodePoolRequest body, e.g. {"nodeVersion": "1.30.5-gke.1000", "imageType": "COS_CONTAINERD"}.
objectYes—≥ 1 characters{"imageType":"COS_CONTAINERD","nodeVersion":"1.30.5-gke.1000"}

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "update": {
    "imageType": "COS_CONTAINERD",
    "nodeVersion": "1.30.5-gke.1000"
  }
}

Output

One shape.

result

FieldTypeExample
ok
boolean—
operation
string—
done
boolean—
status
string—
{
  "done": false,
  "ok": false,
  "operation": "",
  "status": ""
}

See Update Node Pool run in a workflow.

In a technical demo we add the Google Kubernetes Engine connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.