Overview
These steps remove the Helm releases, Kubernetes resources, and external artifacts used by a Poolside upstream Kubernetes deployment. The removal process includes the following phases:- Uninstall the inference stack: Uninstall the
inference-stackHelm release if you deployed local model inference. - Uninstall the platform: Uninstall the
poolside-deploymentHelm release. - Delete cluster resources: Delete the namespaces that Poolside used, which removes the remaining workloads, secrets, ConfigMaps, Ingress objects, and persistent volume claims.
- Clean up external artifacts: Remove remaining artifacts such as DNS records, TLS certificates, container images, the Poolside database, and S3 objects.
Prerequisites
These instructions assume that you deployed Poolside using Install on upstream Kubernetes. Before you start, make sure you have:- Cluster administrator access to the Kubernetes cluster
helm3.12or laterkubectl
Step 1: Uninstall the inference stack
If you deployed local model inference with theinference-stack chart, uninstall it before you remove the application chart.
If you do not run local model inference, skip this step.
List the Helm releases in the poolside-models namespace:
kubectl get pods -n poolside-models shows no Poolside pods remaining:
Step 2: Uninstall the platform
List the Helm releases in thepoolside namespace:
poolside-deployment release:
kubectl get pods -n poolside shows no Poolside pods remaining:
Step 3: Delete cluster resources
Deleting the namespaces removes the remaining workloads, secrets, ConfigMaps, Ingress objects, and persistent volume claims that Poolside created. Delete the Poolside namespaces:Step 4: Clean up external artifacts
Clean up the following external resources separately. Remove only the resources that you no longer need. Container images Delete the Poolside container images and repositories from your registry. The exact procedure depends on the registry you use. S3-compatible object storage Delete the model checkpoints and any audit exports from the bucket you set asglobal.s3.bucket:
--endpoint-url flag and set it to your S3 endpoint URL.
If you customized audit.s3.bucket or audit.s3.prefix, delete audit exports from those values instead of s3://<bucket-name>/audit.
If your bucket only stored Poolside data, you can delete the bucket itself.
PostgreSQL database
Drop the Poolside database and role on your PostgreSQL server. If the database is shared, drop only the Poolside-owned schemas.
TLS certificates and DNS records
Remove the DNS records that pointed to your apiHost and webHost, and revoke or delete the TLS certificates that you issued for those hostnames.
Local files
Delete the extracted Helm bundle directory, your poolside_values.yaml and inference_values.yaml files, and any TLS material (tls.crt, tls.key, ca-bundle.crt) that you kept on your workstation.