Uninstall hybrid runtime

Version 1.15 (latest)

   Supported versions:

• v1.15 (latest)                        
• v1.14                        
• v1.13                         
• List of supported versions

   Unsupported versions:

• v1.12                         
• v1.11                         
• v1.10                                      
• v1.9                                         
• v1.8                                         
• v1.7                                         
• v1.6                                         
• v1.5                                         
• v1.4                                         
• v1.3                                         
• v1.2                                         
• v1.1                                         

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 with apigeectl, see Uninstall 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 your apigee namespace:

   helm uninstall -n APIGEE_NAMESPACE ENV_GROUP_RELEASE_NAME ENV_RELEASE_NAME $ORG_NAME ingress-manager telemetry redis datastore
   

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

   helm uninstall -n APIGEE_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. See Install cert-manager in a custom namespace.

1. Delete the apigee-ca certificate.

     kubectl delete secret -n APIGEE_NAMESPACE apigee-ca

The output should look similar to the following:

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

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

     kubectl get certificates -A
       

The output should look similar to the following:

NAMESPACE   NAME                              READY   SECRET                            AGE
apigee      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 the apigee-ca secret:

     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   AGE
cert-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 the apigee-ca secret in Multi-region deployment on GKE and GKE on-prem.