Get OpenID Configuration

gke.get_openid_config

ActionGoogle Cloudconnection required

Calls GKE API v1 GET .../clusters/{c}/.well-known/openid-configuration.

Read the cluster's OIDC discovery document (issuer, JWKS URI, supported claims). Requires the cluster's OIDC issuer — i.e. Workload Identity — to be enabled; without it GKE answers 400 INVALID_ARGUMENT rather than saying what is missing. Google serves this endpoint without authentication.

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

3 fields, 1 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	—	—	—

Output

One shape.

result

Field	Type	Example
ok	boolean	—
issuer	string	—
jwks_uri	string	—

{
  "issuer": "",
  "jwks_uri": "",
  "ok": false
}

Notes

Needs Workload Identity (the cluster's OIDC issuer) enabled. gke.create_cluster can turn it on with workload_identity=true.

Related Google Kubernetes Engine nodes

See Get OpenID Configuration 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