Uninstallation Guide - AWS (4.3)

These uninstallation steps must be performed in sequence to ensure that all resources are being removed systematically.

Usage Engine Private Edition

Note!

You must delete all ECDs (EC Deployments) prior to uninstalling Usage Engine Private Edition.

You can delete ECDs using Desktop Online in the Manage | Tools & Monitoring | EC Deployment view.

You can also use the command kubectl delete ecd <your ecd name> -n <namespace> to delete the ECD.

To uninstall Usage Engine Private Edition from the Kubernetes cluster, run the following command:

helm uninstall <uepe release name> -n uepe --wait

Wait a few minutes for the External-DNS to cleanup Route53 hosted zone records. All records will be deleted except SOA, NS, and CNAME records.

Hint!

To monitor the hosted zone records cleanup, refresh the Route53 dashboard, Hosted zones | Records section.

Wait for few minutes for the AWS Load Balancer Controller to cleanup EC2 load balancers.

Hint!

To monitor the EC2 load balancers cleanup, refresh the EC2 dashboard, EC2 | Load balancers section.

Proceed to the next step once route53 hosted zone records and EC2 load balancers are cleared.

helm uninstall aws-efs-csi-driver -n uepe

helm uninstall aws-load-balancer-controller -n uepe

helm uninstall external-dns -n uepe

helm uninstall ingress-nginx -n uepe

helm uninstall cert-manager -n cert-manager

If you have restored a RDS database instance from a backup as described in https://infozone.atlassian.net/wiki/spaces/UEPE4D/pages/228491265/Upgrade+Instructions+-+AWS#Restore-database-backup section, ensure that the new database instance is deleted first. However, if no backup restoration was performed, you can disregard this message.

change directory to the terraform script directory

terraform destroy

eksctl delete cluster -f <cluster yaml> --disable-nodegroup-eviction --wait