Uninstall hybrid runtime

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

Helm installations

You can uninstall a Hybrid Helm install with the following commands:

  1. Uninstall the resources in yourapigee namespace:
    helm uninstall -napigeeENV_GROUP_RELEASE_NAMEENV_RELEASE_NAMEORG_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_NAME. In Hybrid v1.11 and newer it is usuallyENV_GROUP_NAME.
    • 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.
  2. After uninstalling the resources in theapigee namespace, uninstallapigee-operator.
    helm uninstall -n apigee-system operator
  3. Delete the Apigee CRDs:
    kubectl delete -k  apigee-operator/etc/crds/default/

apigeectl installations

To deleteApigee components within a specific scope, useapigeectl with the flags for the scope that includes those components:

  • --all-envs: all environment-scope components in all the environments under the organization named in the override config file
  • --datastore: Cassandra.
  • --envenv-name: the environment-scope components: Runtime, Synchronizer, and UDCA
  • --org: the organization-scope components: Apigee Connect Agent, Mart, and Watcher
  • --settings virtualhosts:virtualhost settings only
  • --telemetry: Logger and Metrics

For example:

apigeectl delete -fyour_overrides_file.yaml --org --envenv-name

To deleteonly the Apigee components from the cluster, use this command:

apigeectl delete -fyour_overrides_file.yaml

Use the following commands to deletethe entire Apigee hybrid installation except cert-manager from your cluster:

  1. Runapigeectl delete with the default scope:
    apigeectl delete -fyour_overrides_file.yaml
  2. Verify that the Apigee hybrid components were deleted:
    kubectl -n apigee get apigeedatastore,apigeeredis,apigeetelemetry,org,env,arc

    Your output should be empty

  3. Runapigeectl delete again with--all:Warning:

    Using theapigeectl delete command with the--all flag (for example,apigeectl delete --all -f overrides.yaml) will also delete backup data for all CSI volume snapshots.

    apigeectl delete --all -fyour_overrides_file.yaml

To uninstall cert-manager, seeUninstalling on Kubernetes in the cert-manager documentation.

For more information about theapigeectl command, seeapigeectl.

Use the following command to remove cert-manager:

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.
kubectl -n cert-manager delete secret apigee-ca
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.

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-19 UTC.