How does OCNORA authenticate with Google Kubernetes Engine?

With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.

What can I automate with Google Kubernetes Engine?

38 typed operations, each with a reference page listing its config fields and the shapes it emits.

What if the Google Kubernetes Engine operation I need is not listed?

Where Google Kubernetes Engine has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.

Are there templates that use Google Kubernetes Engine?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Google Kubernetes Engine calls controlled?

Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

Google Kubernetes Engine

Google CloudOAuth 2.0Connection test available

Create, inspect, update and delete GKE clusters and node pools — the full Container API v1 surface (Google OAuth2).

OCNORA ships 38 typed Google Kubernetes Engine operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.

Ask about Google Kubernetes Engine

Before you connect Google Kubernetes Engine

Authentication: OAuth 2.0
Credential: {"client_id", "client_secret", "refresh_token"}
Connection test: Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.

What you can do with Google Kubernetes Engine

Operations, grouped by what they do to your data.

Create and send 3

Read and search 13

Update 14

Delete and cancel 3

Other operations 5

A sample Google Kubernetes Engine workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Kubernetes Engine trigger is needed.
2
Check Autopilot Compatibilitygke.check_autopilot_compatibility
List the incompatibilities that would block migrating this Standard cluster to Autopilot.
3
Cancel Operationgke.cancel_operation
Cancel a running GKE operation. Cancellation is best-effort — some operations cannot be stopped once started.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.

Operations 38