Uninstall Kubernetes Agentic Harness (kube-agents)
SkillCloud & infraDiscovers and removes provisioned kube-agents GCP/GKE infrastructure.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Uninstall Kubernetes Agentic Harness (kube-agents) skill
What this skill tells your AI
The instructions your AI receives, as published by gke-labs/kube-agents in .agents/skills/uninstall-kube-agents/SKILL.md and read by ahel’s review.
Use this skill when asked to remove or uninstall kube-agents infrastructure from a GCP project or GKE cluster.
One-Liner Uninstall Command (Non-Interactive)
To run the project teardown non-interactively:
curl -fsSL https://gke-labs.github.io/kube-agents/uninstall.sh | bash -s -- \
--non-interactive \
--project-id="<PROJECT_ID>" \
--cluster-name="<CLUSTER_NAME>" \
--region="<REGION>"
The engine is lifecycle.sh destroy in terraform/examples/full-install, run against the
install's Terraform state in GCS (bucket <project>-kube-agents-tfstate, prefix
kube-agents/<cluster> — derived from the coordinates, so a fresh clone finds it). Before
terraform destroy it handles the four asymmetries a bare destroy trips over: it forgets the
undeletable KMS resources from state (kept usable in GCP, re-adopted on the next apply), deletes
the PlatformAgent CR and force-clears its finalizer if the operator is wedged, purges every
backup the GKE BackupPlan owns, and clears the cluster's deletion protection.
When the command does not run from a local kube-agents checkout, pass
--source-ref="<SEMVER_TAG_OR_FULL_COMMIT_SHA>" so the teardown engine is fetched at the same
revision that was installed; otherwise it is fetched from main.
terraform must be on PATH — the teardown engine, which this script never installs for you.
See the site's uninstall page.
No Terraform state anywhere (none in GCS, none locally) means one of two things, and the
uninstaller exits 3 without touching anything either way: nothing is installed against
these coordinates, or the install was made by a pre-Terraform release. Only the second is
recoverable here — re-run with --source-ref=<that release> so that release's own teardown
runs instead. Check whether the cluster exists before reaching for a release tag.
Exit 3 is the one non-zero exit that is not a failure; exit 1 means the teardown could not
start or started and did not finish. ./uninstall.sh --help is the contract.
Machine-readable JSON status reports are generated at /tmp/kube-agents-uninstall-report.json.
Signals
- GitHub stars
- 54
- Forks
- 36
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
uninstall-kube-agents- Source
- github.com/gke-labs/kube-agents