Skip to content
NewKubeOn AI: a managed LLM gateway with cost per 1M tokens for every model
KubeOn docs
API referenceReleases

Remove KubeOn

Uninstall the agent, revoke cloud access, clear snapshots and remove the hub or gateway, with what stays behind and how to verify.

On this page

Your workloads are not affected

The agent only reads, and every change from a proposal was applied by your own pipeline. Removing KubeOn changes nothing that runs in your clusters. Export any reports you want to keep first, as CSV or through the API.

1. Remove the agent from each cluster

Helm
helm uninstall kubeon-agent --namespace kubeonkubectl delete namespace kubeon
  • Flux or Argo CD: delete the HelmRelease or Application from your repository and let the controller prune it.
  • Terraform: remove the agent's helm_release resource and apply.
Verify
kubectl get namespace kubeon                              # NotFoundkubectl get clusterrole,clusterrolebinding kubeon-agent-reader   # NotFound

2. Revoke cloud access

AWS
# Billing role, deployed with CloudFormationaws cloudformation delete-stack --stack-name kubeon-billing-accessaws cloudformation wait stack-delete-complete --stack-name kubeon-billing-access# Agent role, one per cluster: remove its policies, then the roleaws iam list-role-policies --role-name <cluster>-kubeon-agent           # inline policiesaws iam delete-role-policy --role-name <cluster>-kubeon-agent --policy-name <policy-name>aws iam list-attached-role-policies --role-name <cluster>-kubeon-agent  # managed policiesaws iam detach-role-policy --role-name <cluster>-kubeon-agent --policy-arn <policy-arn>aws iam delete-role --role-name <cluster>-kubeon-agent

On-premises clusters: delete the credentials you created for the agent's snapshot upload. Your billing exports, the CUR, Glue and Athena tables, BigQuery datasets and Azure exports were created by you and are left as they are.

3. Clear snapshots

The snapshot bucket's lifecycle rule deletes every snapshot within 14 days. To remove them now from your own bucket:

Amazon S3
aws s3 rm s3://<snapshot-bucket>/<prefix>/ --recursive

4. Remove the hub

HubHow to remove itYour data
KubeOn CloudAsk us to close the workspaceDeleted or kept as agreed in your evaluation or contract
Self-hosted on AWSRun terraform destroy in the hub's Terraform directoryTake a final database snapshot first if you want to keep cost history
Self-hosted on Kubernetes or on-premiseshelm uninstall kubeon-hub --namespace kubeon-hub, then remove the database, Redis and buckets you created for itYours, until you delete it

5. Remove the KubeOn AI gateway

  1. Point each application back at its provider's endpoint, or another route, and deploy. Revoking keys first would make those requests fail.
  2. Revoke the gateway's team and application keys.
  3. Self-hosted: helm uninstall kubeon-ai-gateway --namespace kubeon-ai.
  4. Remove the provider credentials created for the gateway, such as the Bedrock role or the Azure OpenAI workload identity, and the read-only billing access for AI tokenomics.

What stays

After removal
Your clusters and workloadsUnchanged. KubeOn never modified them
Changes applied from proposalsIn your repository's history, like any other change
Your billing exports and datasetsUnchanged, and still delivered by your cloud provider
Reports you exported or scheduled to emailWherever you saved or sent them
Need help with this guide?Contact support
PreviousUpgrades and rollbackNext Connect AWS billing