Google GKE On-Prem
Google CloudOAuth 2.0Connection test available
GKE On-Prem (Google OAuth2).
OCNORA ships 11 typed Google GKE On-Prem 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.
Before you connect Google GKE On-Prem
- 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 GKE On-Prem
Operations, grouped by what they do to your data.
Create and send 2
Read and search 4
Delete and cancel 2
Other operations 1
A sample Google GKE On-Prem workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google GKE On-Prem trigger is needed.
- 2Get Bare Metal Clustergke_on_prem.get_bare_metal_clusterGets details of a single bare metal Cluster.
- 3Create Bare Metal Clustergke_on_prem.create_bare_metal_clusterCreates a new bare metal cluster in a given project and location.
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 11
- Create Bare Metal ClusterCreates a new bare metal cluster in a given project and location.gke_on_prem.create_bare_metal_cluster
- Create Vmware ClusterCreates a new VMware user cluster in a given project and location.gke_on_prem.create_vmware_cluster
- Delete Bare Metal ClusterDeletes a single bare metal Cluster.gke_on_prem.delete_bare_metal_cluster
- Delete Vmware ClusterDeletes a single VMware Cluster.gke_on_prem.delete_vmware_cluster
- Enroll Vmware ClusterEnrolls an existing VMware user cluster and its node pools to the Anthos On-Prem API within a given project and location.gke_on_prem.enroll_vmware_cluster
- Get Bare Metal ClusterGets details of a single bare metal Cluster.gke_on_prem.get_bare_metal_cluster
- Get Vmware ClusterGets details of a single VMware Cluster.gke_on_prem.get_vmware_cluster
- List Bare Metal ClustersLists bare metal clusters in a given project and location.gke_on_prem.list_bare_metal_clusters
- List Vmware ClustersLists VMware Clusters in a given project and location.gke_on_prem.list_vmware_clusters
- Update Bare Metal ClusterUpdates the parameters of a single bare metal Cluster.gke_on_prem.update_bare_metal_cluster
- Update Vmware ClusterUpdates the parameters of a single VMware cluster.gke_on_prem.update_vmware_cluster
Google GKE On-Prem questions
- How does OCNORA authenticate with Google GKE On-Prem?
- 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 GKE On-Prem?
- 11 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google GKE On-Prem operation I need is not listed?
- Where Google GKE On-Prem 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 GKE On-Prem?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google GKE On-Prem 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.
See your first Google GKE On-Prem workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.