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 To uninstall Usage Engine Private Edition from the Kubernetes cluster, run the following command:kubectl delete ecd <your ecd name> -n <namespace> to delete the ECD.helm uninstall <uepe release name> -n uepe --wait
Hint!
To monitor the hosted zone records cleanup, refresh the AzureDNS console, Zone details | RECORD SETS section.
Kubernetes Cluster Add-ons
To uninstall Add-ons from the Kubernetes cluster, run:
helm uninstall ingress-azure -n uepe
helm uninstall external-dns -n uepe
helm uninstall ingress-nginx -n uepe
Cert Manager
To uninstall cert-manager from the Kubernetes cluster, run:
helm uninstall cert-manager -n cert-manager
Azure Resources
Delete the Persistent Volume Claim (PVC) and Persistent Volume (PV) if they had been created earlier. Change directory to the terraform script directory. Change directory to the manifests directory.
cd <terraform script directory>/manifests
kubectl delete -f storage_persistence.yaml -n uepe
Note!
The following notes are relevant only if you have performed a backup or restore as described in upgrade instructions Upgrade Instructions - Azure (4.2). If no upgrade was performed, you can disregard this section.
If you have created on-demand snapshot backups for database and file storage, ensure that backup protection is disabled and that all backup data is deleted. See https://learn.microsoft.com/en-us/azure/backup/manage-azure-database-postgresql#stop-protection and https://learn.microsoft.com/en-us/azure/backup/manage-afs-backup#stop-protection-on-a-file-share for guidance.
If you have restored a PostgreSQL flexible server database instance from a backup as described in https://infozone.atlassian.net/wiki/spaces/UEPE4D/pages/269484079/Upgrade+Instructions+-+Azure+4.2#Restore-database-backup section, ensure that the new database instance is deleted first. If no backup restoration was performed, you can disregard from this.
Change directory to the terraform script directory and run the following command to remove all Azure resources created (cluster, VNET, persistent storage etc):
terraform destroy