Uninstall Icebreaker
This walks through undoing the Get Started flow, in reverse order, so you can run through the install again from a clean state — useful when testing the install docs themselves, or re-evaluating with a different configuration.
1. Delete the Admin console resources
Section titled “1. Delete the Admin console resources”Reverse of Set up a Data Server — the Icebreaker Agent tears down the matching cluster resources (Deployments, NodePools) as soon as you delete each one in the console:
- Navigate to your Icebreaker Agent in the Admin console.
- Under Data Servers, delete the Data Server(s) you created.
- Under Compute Specs, delete the Capacity Policy(ies) you created.
- Back at the Account level, under Data Catalogs, delete the Data Catalog entry.
- From the Icebreaker Agents list, click Delete next to the Agent to remove its record and token from the control plane. This doesn’t touch anything already running in your cluster — the next steps handle that.
2. Uninstall the Icebreaker Agent
Section titled “2. Uninstall the Icebreaker Agent”Reverse of Install the Icebreaker Agent:
helm uninstall icebreaker-agent --namespace eyrie-compute3. Delete the Agent token Secret
Section titled “3. Delete the Agent token Secret”kubectl delete secret icebreaker-agent-token -n eyrie-compute4. Delete the workload namespace (optional)
Section titled “4. Delete the workload namespace (optional)”kubectl delete namespace eyrie-compute5. Remove the Lakekeeper evaluation deployment (optional)
Section titled “5. Remove the Lakekeeper evaluation deployment (optional)”If you deployed Lakekeeper via Evaluate Icebreaker with Lakekeeper and want to reset that too:
helm uninstall icebreaker-lakekeeper --namespace lakekeeperkubectl delete namespace lakekeeperThis does not delete the S3 bucket, IAM role/policies, or warehouse data you set up for Lakekeeper — remove those separately if you want a fully clean AWS account.
What you have at this point
Section titled “What you have at this point”- No Icebreaker Agent is running in your cluster, and its record in the Admin console is deleted (or shows as not connected, if you skipped that step).
- Your EKS cluster and its prerequisites (Karpenter, ingress controller, ACM certificate, DNS) are untouched and ready for a fresh install.
Start over from Install the Icebreaker Agent.