kube-agents: Skill for Claude Code

Uninstall Kubernetes Agentic Harness (kube-agents)

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, use the uninstall.sh published for the release the install runs, substituting <RELEASE_VERSION> with a release tag from GitHub Releases. The release-pinned script tears the install down with its own release's engine; a copy carrying no baked version falls back to the engine on main, which is not the one that built the install:

curl -fsSL https://raw.githubusercontent.com/gke-labs/kube-agents/<RELEASE_VERSION>/uninstall.sh | bash -s -- \
  --non-interactive \
  --gcp-project-id="<PROJECT_ID>" \
  --gke-cluster-name="<CLUSTER_NAME>" \
  --gcp-region="<REGION>"

On a GitLab install, the installer creates the token Secret, and the CA Secret for a private CA, outside the Helm release. A teardown that deletes the cluster deletes them too. On a cluster that the teardown keeps, tell the operator that the Secrets stay, and give the command in "What a teardown leaves" on the site's uninstall page (docs/site/src/content/docs/install/uninstall.md), or tell the operator to delete the namespace. That command sources the install's install.env in a subshell, the same way the installer reads it, so renamed Secrets or a non-default namespace are found. Then tell the operator to revoke the token in GitLab, and the read-only token too, if the operator made one.

The installer finds install.env in this order: KUBE_AGENTS_INSTALL_ENV, beside install.sh, in the current directory, then the source directory ($HOME/kube-agents under curl … | bash).

Also tell the operator to revoke the token in GitLab, and the read-only token too, if the operator made one.

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 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, uninstalls the Helm releases with the helm CLI on a cluster the install did not create, purges every backup the GKE BackupPlan owns, and clears the cluster's deletion protection.