Set Node Locations
gke.set_locations
ActionGoogle Cloudconnection required
Calls GKE API v1 POST .../clusters/{c}:setLocations.
Set the zones the cluster's nodes run in. Adding a zone creates nodes there; removing one deletes them.
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
4 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
location Zone or region of the cluster (overrides connection). | string | No | — | — | — |
cluster Cluster name. | string | Yes | — | — | — |
locations Zones the cluster's nodes should run in, e.g. us-central1-a,us-central1-b. | array | Yes | — | ≥ 1 characters; array of string | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
operation | string | — |
done | boolean | — |
status | string | — |
{
"done": false,
"ok": false,
"operation": "",
"status": ""
}See Set Node Locations 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.