Google Cloud · Cloud service
Google Kubernetes Engine with OrchestrAI
Catalog exported 2026-09-02
Create, list, and delete GKE clusters from chat, with cluster deletion protected by a typed risk phrase.
OrchestrAI exposes 3 GKE operations: 1 is low-risk (read-only or low-impact), 1 create or modify resources and run only after you confirm the plan, and 1 is destructive and requires a typed risk phrase. 1 of them also carries a step-level approval gate.
What teams use it for
Small infrastructure teams use OrchestrAI to bring up a GKE cluster for a new project or a short-lived preview environment, then tear it down when the work is over. Listing clusters across regions is a quick way to spot forgotten ones that are still costing money. Node pool changes and cluster version upgrades are not covered, so scaling nodes or moving to a newer GKE release still runs through gcloud.
Every GKE operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
List GKE Clusters |
List all Google Kubernetes Engine clusters | Low risk | No |
Create GKE Cluster |
Create a new Google Kubernetes Engine cluster | Creates resources | No |
Delete GKE Cluster |
Delete a Google Kubernetes Engine cluster | Destructive | Yes |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
Prompts that work
- Create a GKE cluster named preview-42 in us-central1 with 2 nodes
- Show me every GKE cluster in this project with its region and node count
- Delete the GKE cluster preview-42, it is no longer needed
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- How does OrchestrAI protect against accidentally deleting a GKE cluster?
- Cluster deletion is critical risk. Before it runs, OrchestrAI shows what will be removed and requires a typed risk phrase, so a casual message cannot trigger it.
- Can OrchestrAI resize a GKE node pool?
- Not at the moment, because the available GKE operations are create cluster, list clusters, and delete cluster.
- Which GKE operations need an extra approval step?
- One operation carries a step-level approval gate on top of plan confirmation: Delete GKE Cluster. It is classed destructive and cannot run without a typed risk phrase.
Other Google Cloud services
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.