Set Addons

gke.set_addons
ActionGoogle Cloudconnection required

Calls GKE API v1 POST .../clusters/{c}:setAddons.

Enable or disable cluster addons (HTTP load balancing, DNS cache, Config Connector, GCE persistent-disk CSI driver…).

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.

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
location
Zone or region of the cluster (overrides connection).
stringNo———
cluster
Cluster name.
stringYes———
addons_config
An AddonsConfig object, e.g. {"httpLoadBalancing": {"disabled": false}}.
objectYes—≥ 1 characters{"httpLoadBalancing":{"disabled":false}}

Example configuration

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

{
  "addons_config": {
    "httpLoadBalancing": {
      "disabled": false
    }
  }
}

Output

One shape.

result

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

See Set Addons 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.