Overview
These steps remove theinference Helm release, its Kubernetes resources, and the AWS artifacts used by a model inference deployment on Amazon EKS.
The removal process includes the following phases:
- Uninstall the inference release: Uninstall the
inferenceHelm release, which also tears down the Application Load Balancer. - Delete cluster resources: Delete the
poolside-modelsnamespace, which removes the remaining workloads, secrets, ConfigMaps, and Ingress objects. - Clean up AWS artifacts: Remove the IRSA role, ECR repository, S3 checkpoints, ACM certificate, and DNS records.
Prerequisites
These instructions assume that you deployed model inference using Install on Amazon EKS. Before you start, make sure you have:- Cluster administrator access to the EKS cluster
helm3.12or laterkubectl, configured for your EKS clusterawsCLI, with permission to delete the AWS resources you provisioned
Step 1: Uninstall the inference release
List the Helm releases in thepoolside-models namespace:
kubectl get pods -n poolside-models shows no Poolside pods remaining:
Step 2: Delete cluster resources
Deleting the namespace removes the remaining workloads, secrets, ConfigMaps, and any Ingress objects that the inference release created:Step 3: Clean up AWS artifacts
Clean up the following AWS resources separately. Remove only the resources that you no longer need. IRSA role Delete the inference-pod IAM role and its permissions policy. If you created them witheksctl create iamserviceaccount, delete them with eksctl:
aws iam commands you use for IAM cleanup.
Amazon ECR
Delete the atlas repository if no other deployment uses it:
models.<key>.model in the inference_values.yaml file you used to install:
inference_values.yaml file from your workstation.