Update Cluster

gke.update_cluster

ActionGoogle Cloudconnection required

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

Apply a ClusterUpdate. The API accepts one desired* field per call, so change one thing at a time.

Ask about Google Kubernetes Engine All Google Kubernetes Engine 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

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	—	—	—
update A ClusterUpdate object, e.g. {"desiredMasterVersion": "1.30"}. The API accepts one desired* field per call.	object	Yes	—	≥ 1 characters	{"desiredMasterVersion":"1.30"}

Example configuration

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

{
  "update": {
    "desiredMasterVersion": "1.30"
  }
}

Output

One shape.

result

Field	Type	Example
ok	boolean	—
operation	string	—
done	boolean	—
status	string	—

{
  "done": false,
  "ok": false,
  "operation": "",
  "status": ""
}

Related Google Kubernetes Engine nodes

See Update Cluster 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.

Book a technical demo Talk to sales