Integration · Kubernetes
Helm + OrchestrAI
Catalog exported 2026-09-02 · Helm website
Install, upgrade, roll back, and uninstall Helm releases from chat with confirmation at every step.
OrchestrAI exposes 31 Helm operations: 11 are low-risk (read-only or low-impact), 18 create or modify resources and run only after you confirm the plan, and 2 are destructive and require a typed risk phrase. 20 of them also carry a step-level approval gate.
What teams use it for
Kubernetes operators use OrchestrAI to render a chart locally, review its default values, and then install or upgrade the release once they are satisfied. Repo add and update, install, and template review are medium or low risk. Upgrading and rolling back a release are high risk and confirmed, and uninstalling is critical, which means a typed risk phrase is required. There is no operation for helm diff, packaging a chart, or pushing to an OCI registry, so those steps stay on the command line.
Every Helm operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Helm History |
Get release history | Low risk | No |
Helm List |
List Helm releases | Low risk | No |
Helm Repo List |
List Helm repositories | Low risk | No |
Helm Show Values |
Show default values for a chart | Low risk | No |
Helm Status |
Get status of a Helm release | Low risk | No |
Helm Template |
Render chart templates locally | Low risk | No |
Kubectl Describe |
Describe a Kubernetes resource | Low risk | No |
Kubectl Get |
Get Kubernetes resources | Low risk | No |
Kubectl Get Namespaces |
List all namespaces | Low risk | No |
Kubectl Logs |
Get pod logs | Low risk | No |
Kubectl Rollout Status |
Check rollout status | Low risk | No |
Create Velero Backup |
Create Kubernetes backup with Velero | Creates resources | Yes |
Helm Install |
Install a Helm chart | Creates resources | Yes |
Helm Repo Add |
Add a Helm repository | Creates resources | Yes |
Helm Repo Update |
Update Helm repositories | Creates resources | Yes |
Kubectl Copy |
Copy files to/from a pod | Creates resources | Yes |
Kubectl Create |
Create a Kubernetes resource | Creates resources | Yes |
Kubectl Port Forward |
Forward ports to a pod or service | Creates resources | Yes |
Add Cluster to ArgoCD |
Add a Kubernetes cluster to ArgoCD | Modifies existing | Yes |
CPU Stress Test |
Apply CPU stress to target | Modifies existing | Yes |
Create Network Partition |
Create network partition between services | Modifies existing | Yes |
Helm Rollback |
Rollback a Helm release to a previous revision | Modifies existing | Yes |
Helm Upgrade |
Upgrade a Helm release | Modifies existing | Yes |
Inject Chaos Failure |
Inject failure into service (pod-kill, latency, etc.) | Modifies existing | Yes |
Kubectl Apply |
Apply a manifest to the cluster | Modifies existing | Yes |
Kubectl Exec |
Execute a command in a pod | Modifies existing | Yes |
Kubectl Rollout Restart |
Restart a rollout | Modifies existing | Yes |
Kubectl Rollout Undo |
Undo a rollout | Modifies existing | Yes |
Restore from Velero Backup |
Restore Kubernetes from Velero backup | Modifies existing | Yes |
Helm Uninstall |
Uninstall a Helm release | Destructive | Yes |
Kubectl Delete |
Delete a Kubernetes resource | 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.
What you connect
A Helm credential (stored as argocd, kubernetes, velero).
Connected-service tokens are envelope-encrypted with a per-record key wrapped by a cloud KMS.
Prompts that work
- Show the default values for bitnami/redis and render the templates with replicas set to 3
- Upgrade the ingress-nginx release in namespace ingress to chart version 4.11.2
- Roll back the api-gateway release to revision 7
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
- Does OrchestrAI confirm before upgrading a Helm release?
- Yes. Upgrade is high risk because it modifies a running release, so OrchestrAI shows the chart version and values and waits for your approval.
- What is required to uninstall a Helm release through OrchestrAI?
- Uninstall is classified as critical. It waits for confirmation and requires you to type a risk phrase, since it removes the workload and its resources.
- How does OrchestrAI authenticate to Helm?
- You add a Helm credential once in the connections screen. It is envelope-encrypted with a per-record key wrapped by a cloud KMS and is only decrypted inside the run that needs it.
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.