Set Node Pool Management

gke.set_node_pool_management
ActionGoogle Cloudconnection required

Calls GKE API v1 POST .../nodePools/{np}:setManagement.

Set auto-upgrade and auto-repair for one node pool.

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

7 fields, 2 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———
auto_upgrade
Let GKE upgrade these nodes automatically. Leave unset to keep the current value.
booleanNo———
auto_repair
Let GKE repair unhealthy nodes automatically. Leave unset to keep the current value.
booleanNo———
management
A full NodeManagement object; wins over the fields above.
objectNo———
  • At least one of auto_upgrade, auto_repair, management must be set.

Output

One shape.

result

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

See Set Node Pool Management 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.