Deleting the API Connect deployment in a Kubernetes runtime environment

To delete the Kubernetes deployment of API Connect, you delete the Helm charts, Custom Resource Definitions, the Persistent Volumes, and the namespace.

About this task

To delete the API Connect deployment in a Kubernetes runtime environment, you will need the Kubernetes command-line tool, kubectl. For more information, see kubectl.

Procedure

Repeat the following steps for each namespace containing an API Connect subsystem:

  1. List the Helm charts in your namespace by entering: helm ls --namespace=<namespace>. You will perform a delete for each chart. The charts will look similar to the following:
    • dynamic-gateway-service-*
    • cassandra-operator-*
    • dynamic-gateway-*
    • apic-analytics-*
    • apiconnect-*
    • apic-portal-*
  2. Delete each Helm chart using the --purge option: Helm delete --purge <chart-name>. If the reclaim policy of a Persistent Volume is Delete, the PV is automatically deleted when the Helm chart is deleted.
  3. List and delete the Custom Resource Definitions (CRDs). Enter kubectl get crd to list the CRDs. Delete the following API Connect CRDs by entering the following command: kubectl delete crd <name>:
    • cassandraclusters.apic.ibm.com
    • cassandraclusterbackups.apic.ibm.com
  4. Check if there are remaining Persistent Volumes associated with API Connect by entering: kubectl get pv. If there are any remaining PV, delete them manually using the following command: kubectl delete pv <name>.
  5. Delete the namespace if it is no longer needed. Ensure there are no other resources deployed in the namespace before deleting it. Enter the following command to delete the namespace: kubectl delete namespace <name>.