You are currently viewing version 1.13 of the Apigee hybrid documentation.This version is end of life. You should upgrade to a newer version. For more information, seeSupported versions.

Uninstall Apigee hybrid

Note: These commands are procedures are intended to uninstall hybrid installations managed with Helm. If you are uninstalling an earlier version of Apigee hybrid managed withapigeectl, seeUninstall hybrid runtime in the hybrid v1.11 documentation for uninstallation procedures.

Use the following commands to uninstall the hybrid runtime:

1. Uninstall the resources in yourapigee namespace:

   helm uninstall -nAPIGEE_NAMESPACEENV_GROUP_RELEASE_NAMEENV_RELEASE_NAME$ORG_NAME ingress-manager telemetry redis datastore

   • ENV_GROUP_RELEASE_NAME is the name with which you previously installed theapigee-virtualhost chart. In hybrid v1.10, it is usuallyapigee-virtualhost-ENV_GROUP. In Hybrid v1.11 and newer it is usuallyENV_GROUP.
   • ENV_RELEASE_NAME is the name with which you previously installed theapigee-env chart. In hybrid v1.10, it is usuallyapigee-env-ENV_NAME. In Hybrid v1.11 and newer it is usuallyENV_NAME.
   • ORG_NAME is the name with which you previously installed theapigee-org chart. It is usually your organization name. If you have defined anORG_NAME environment variable, you can use that variable in your command.
2. Uninstallapigee-operator.

   helm uninstall -nAPIGEE_NAMESPACE operator

3. Delete the Apigee CRDs:

   kubectl delete -k  apigee-operator/etc/crds/default/

Remove cert-manager

To remove cert-manager, permanently remove the apigee-ca certificate and secret from the cert-manager namespace with the following steps:

Note: If you are running cert-manager in a custom namespace, replace cert-manager with your custom cert-manager namespace in the following commands. SeeInstall cert-manager in a custom namespace.Note: Some Google Distributed Cloud versions come with their own bundled version of cert-manager. If for certain reasons, you need to remove this bundled cert-managar and install your own cert-manager, follow the instructions inConflictingcert-manager installation to avoid conflicts.

1. Delete theapigee-ca certificate.

   kubectl delete secret -nAPIGEE_NAMESPACE apigee-ca

The output should look similar to the following:

certificate.cert-manager.io "apigee-ca" deleted

2. Verify that theapigee-ca certificate was deleted by getting all certificates:

   kubectl get certificates -A

The output should look similar to the following:

NAMESPACE   NAME                              READY   SECRET                            AGEapigee      apigee-datastore-guardrails-tls   True    apigee-datastore-guardrails-tls   89m

Note: the certificate does not get recreated. The secret remains after the certificate was deleted. You can verify this by getting the secrets:.

kubectl get secrets -n cert-manager

3. Delete theapigee-casecret:

   kubectl -n cert-manager delete secret apigee-ca

4. Verify that the secret was deleted:

   kubectl get secrets -n cert-manager

The output should look similar to the following:

NAME                    TYPE   DATA AGEcert-manager-webhook-ca Opaque 3    94m

If you have a multi-region installation, and you want to install Apigee hybrid again on the same region, you need to follow the instructions for copying theapigee-ca secret inMulti-region deployment on GKE and GKE on-prem.