ENV_GROUP_RELEASE_NAME é o nome com que você instalou anteriormente o gráfico apigee-virtualhost. Na versão híbrida v1.10, geralmente é
apigee-virtualhost-ENV_GROUP. Na versão híbrida v1.11 e mais recentes, geralmente é
ENV_GROUP.
ENV_RELEASE_NAME é o nome com que você instalou anteriormente o gráfico apigee-env. Na versão híbrida v1.10, geralmente é
apigee-env-ENV_NAME. Na versão híbrida v1.11 e mais recentes, geralmente é
ENV_NAME.
ORG_NAME é o nome com que você instalou anteriormente o gráfico apigee-org. Geralmente é o nome da sua organização. Se você definiu uma variável de ambiente ORG_NAME, pode usá-la no seu comando.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-18 UTC."],[],[],null,["# Uninstall hybrid runtime\n\nUninstall Apigee hybrid\n-----------------------\n\n| **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](/apigee/docs/hybrid/v1.11/uninstall#apigeectl-installations) in the hybrid v1.11 documentation for uninstallation procedures.\n\nUse the following commands to uninstall the hybrid runtime:\n\n1. Uninstall the resources in your `apigee` namespace: \n\n ```\n helm uninstall -n APIGEE_NAMESPACE ENV_GROUP_RELEASE_NAME ENV_RELEASE_NAME $ORG_NAME ingress-manager telemetry redis datastore\n ```\n - \u003cvar translate=\"no\"\u003eENV_GROUP_RELEASE_NAME\u003c/var\u003e is the name with which you previously installed the `apigee-virtualhost` chart. In hybrid v1.10, it is usually `apigee-virtualhost-`\u003cvar translate=\"no\"\u003eENV_GROUP\u003c/var\u003e. In Hybrid v1.11 and newer it is usually \u003cvar translate=\"no\"\u003eENV_GROUP\u003c/var\u003e.\n - \u003cvar translate=\"no\"\u003eENV_RELEASE_NAME\u003c/var\u003e is the name with which you previously installed the `apigee-env` chart. In hybrid v1.10, it is usually `apigee-env-`\u003cvar translate=\"no\"\u003eENV_NAME\u003c/var\u003e. In Hybrid v1.11 and newer it is usually \u003cvar translate=\"no\"\u003eENV_NAME\u003c/var\u003e.\n - \u003cvar translate=\"no\"\u003eORG_NAME\u003c/var\u003e is the name with which you previously installed the `apigee-org` chart. It is usually your organization name. If you have defined an \u003cvar translate=\"no\"\u003eORG_NAME\u003c/var\u003e environment variable, you can use that variable in your command.\n2. Uninstall `apigee-operator`. \n\n ```\n helm uninstall -n APIGEE_NAMESPACE operator\n ```\n3. Delete the Apigee CRDs: \n\n ```\n kubectl delete -k apigee-operator/etc/crds/default/\n ```\n\n### Remove cert-manager\n\n\nTo remove cert-manager, permanently remove the apigee-ca certificate and secret from the cert-manager namespace with\nthe following steps:\n| 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](/apigee/docs/hybrid/v1.15/install-cert-manager#install-cert-manager-in-a-custom-namespace).\n\n1. Delete the `apigee-ca` certificate. \n\n ```\n kubectl delete secret -n APIGEE_NAMESPACE apigee-ca\n ```\n2. The output should look similar to the following: \n\n```\n certificate.cert-manager.io \"apigee-ca\" deleted\n \n```\n3. Verify that the `apigee-ca` certificate was deleted by getting all certificates: \n\n ```\n kubectl get certificates -A\n \n ```\n4. The output should look similar to the following: \n\n```\nNAMESPACE NAME READY SECRET AGE\napigee apigee-datastore-guardrails-tls True apigee-datastore-guardrails-tls 89m\n \n```\n| Note: the certificate does not get recreated. The secret remains after the certificate was deleted. You can verify this by getting the secrets:. \n|\n| ```\n| kubectl get secrets -n cert-manager\n| \n| ```\n5. Delete the `apigee-ca `secret: \n\n ```\n kubectl -n cert-manager delete secret apigee-ca\n \n ```\n6. Verify that the secret was deleted: \n\n ```\n kubectl get secrets -n cert-manager\n \n ```\n7. The output should look similar to the following: \n\n```\nNAME TYPE DATA AGE\ncert-manager-webhook-ca Opaque 3 94m\n \n```\n\n| 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\n| deployment on GKE and GKE on-prem](/apigee/docs/hybrid/v1.15/multi-region#set-up-the-new-region)."]]
