Uninstall VMware Telco Cloud Service Assurance through VMware Telco Cloud Automation

To uninstall the VMware Telco Cloud Service Assurance deployment, you must first terminate the CNF instantiation and then run the cleanup action script.

Procedure

Terminate the CNF in the reverse order of their instantiation from the VMware Telco Cloud Automation manager UI.
1. Terminate tcsa (VMware Telco Cloud Service Assurance).
  - From the VMware Telco Cloud Automation UI, navigate to Inventory > Network Function. Click on the three dots against the VMware Telco Cloud Service Assurance CNF which you want to uninstall. Select the option Terminate. Verify the termination job is completed for the CNF.
  - Use kubectl command to manually check the status of VMware Telco Cloud Service Assurance CNF while checking for the corresponding Custom Resource which is tcxproduct. While deleting VMware Telco Cloud Service Assurance, Kubernetes returns the following information:
```
root [ ~/base/tcx-deployer/scripts ]# kubectl get tcxproduct
tcsa-201-0b814-9pgbl   deleteInitiated   False   Deleting the TCX Product
```
  - Upon successful deletion, the following command returns a NotFound error.
```
root [ ~/base/tcx-deployer/scripts ]# kubectl get tcxproduct tcsa-201-0b814-9pgbl
Error from server (NotFound): tcxproducts.tcx.vmware.com "tcsa-201-0b814-9pgbl" not found
```
  - If the tcxproduct is not deleted within a few minutes, then follow the troubleshooting steps to determine the status of VMware Telco Cloud Service Assurance. For more information about the troubleshooting steps, see Getting Additional Information for CNFs in the Troubleshooting Guide.

Run the cleanup core command.

cd $TCSA_WORK_SPACE/tcx-deployer/clis
tcxctl cleanup core --kubeconfig path-to-your-kubeconfig [--namespace <namespace>]

Run the cleanup action using the installer.

root [ ~ ]# cd $TCSA_WORK_SPACE/tcx-deployer/clis
root [ ~/base/tcx-deployer/clis ]# ./tcxctl cleanup registry --registry <secure-harbor-registry-fqdn>/<project-name> --registry-password <your-registry-password> --registry-username <your-registry-username> --registry-cert <path-to-your-registry-ca-certificate-file> [--force]