> [!CAUTION]
> You are currently viewing version 1.14 of the Apigee hybrid documentation. For more information, see [Supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions).

<button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">Version 1.14 </button>

- Supported versions:
- [v1.17 (latest)](https://docs.cloud.google.com/apigee/docs/hybrid/v1.17/uninstall.md.txt)
- [v1.16](https://docs.cloud.google.com/apigee/docs/hybrid/v1.16/uninstall.md.txt)
- [v1.15](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/uninstall.md.txt)
- [v1.14](https://docs.cloud.google.com/apigee/docs/hybrid/v1.14/uninstall.md.txt)
- [List of supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions)
- Unsupported versions:
- [v1.13](https://docs.cloud.google.com/apigee/docs/hybrid/v1.13/uninstall.md.txt)
- [v1.12](https://docs.cloud.google.com/apigee/docs/hybrid/v1.12/uninstall.md.txt)
- [v1.11](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/uninstall.md.txt)
- [v1.10](https://docs.cloud.google.com/apigee/docs/hybrid/v1.10/uninstall.md.txt)
- [v1.9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.9/uninstall.md.txt)
- [v1.8](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/uninstall.md.txt)
- [v1.7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/uninstall.md.txt)
- [v1.6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.6/uninstall.md.txt)
- [v1.5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.5/uninstall.md.txt)
- [v1.4](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/uninstall.md.txt)
- [v1.3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.3/uninstall.md.txt)
- [v1.2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/uninstall.md.txt)
- [v1.1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.1/uninstall.md.txt)

## Uninstall Apigee hybrid

> [!NOTE]
> **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](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/uninstall.md.txt#apigeectl-installations) 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
   ```
   - <var translate="no">ENV_GROUP_RELEASE_NAME</var> 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 <var translate="no">ENV_GROUP</var>.
   - <var translate="no">ENV_RELEASE_NAME</var> 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 <var translate="no">ENV_NAME</var>.
   - <var translate="no">ORG_NAME</var> is the name with which you previously installed the `apigee-org` chart. It is usually your organization name. If you have defined an <var translate="no">ORG_NAME</var> 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]
> **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](https://docs.cloud.google.com/apigee/docs/hybrid/v1.14/install-cert-manager.md.txt#install-cert-manager-in-a-custom-namespace).

> [!NOTE]
> **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 in [Conflicting `cert-manager` installation](https://cloud.google.com/anthos/clusters/docs/on-prem/1.13/known-issues#conflicting-cert-manager-installation) to avoid conflicts.

1. Delete the `apigee-ca` certificate.

   ```
     kubectl delete secret -n APIGEE_NAMESPACE apigee-ca
   ```
2. The output should look similar to the following:

```
  certificate.cert-manager.io "apigee-ca" deleted
  
```
3. Verify that the `apigee-ca` certificate was deleted by getting all certificates:

   ```
     kubectl get certificates -A
       
   ```
4. 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]
> 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
>     
> ```

5. Delete the `apigee-ca `secret:

   ```
     kubectl -n cert-manager delete secret apigee-ca
       
   ```
6. Verify that the secret was deleted:

   ```
     kubectl get secrets -n cert-manager
       
   ```
7. The output should look similar to the following:

```
NAME                      TYPE     DATA   AGE
cert-manager-webhook-ca   Opaque   3      94m
    
```

> [!NOTE]
> 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](https://docs.cloud.google.com/apigee/docs/hybrid/v1.14/multi-region#set-up-the-new-region).