Azure · Cloud service
Azure Kubernetes Service with OrchestrAI
Catalog exported 2026-09-02
Create, list, and delete AKS clusters from chat, with a typed risk phrase required before any deletion.
OrchestrAI exposes 3 AKS 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
Founders and small platform teams use OrchestrAI to get an AKS cluster running for a first deployment without learning the full az aks flag set. Listing every cluster in the subscription with its resource group is a routine check before a cost review. There is no node pool, scale, or upgrade operation, so changing node counts or moving to a newer Kubernetes version still requires az aks commands.
Every AKS operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
List AKS Clusters |
List all Azure Kubernetes Service clusters | Low risk | No |
Create AKS Cluster |
Create a new Azure Kubernetes Service cluster | Creates resources | No |
Delete AKS Cluster |
Delete an Azure Kubernetes Service 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 an AKS cluster named app-aks in rg-app in westeurope with 3 Standard_D2s_v5 nodes
- List all AKS clusters in my subscription
- Delete the AKS cluster demo-aks in rg-demo
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
- What does OrchestrAI do before deleting an AKS cluster?
- It classifies the deletion as critical, shows the cluster and everything that will go with it, and waits for a typed risk phrase. Nothing runs until that phrase is entered.
- Can OrchestrAI upgrade an AKS cluster?
- Not in the current toolset, where create, list, and delete are the three AKS operations available.
- Which AKS operations need an extra approval step?
- One operation carries a step-level approval gate on top of plan confirmation: Delete AKS Cluster. It is classed destructive and cannot run without a typed risk phrase.
Other Azure 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.