Set Node Pool Autoscaling

gke.set_node_pool_autoscaling
ActionGoogle Cloudconnection required

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

Turn cluster autoscaling on or off for one node pool, and set its bounds.

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

8 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———
enabled
Turn autoscaling on. Off shrinks the pool to a fixed size.
booleanNo———
min_nodes
Minimum nodes per zone when enabled.
numberNo—≥ 0—
max_nodes
Maximum nodes per zone. Required when enabling.
numberNo—≥ 0—
autoscaling
A full NodePoolAutoscaling object; wins over the fields above.
objectNo———

Output

One shape.

result

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

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