Exclua a instância da Apigee no contexto que você acabou de selecionar:
Exclua um componente de cada vez.
helm -n apigee delete datastore
helm -n apigee delete telemetry
helm -n apigee delete ingress-manager
helm -n apigee delete redis
helm -n apigee delete ORG_NAME
Repita o comando a seguir para cada ambiente:
helm -n apigee delete ENV_NAME
Repita o comando a seguir para cada grupo de ambientes:
helm -n apigee delete ENV_GROUP_NAME
helm -n apigee-system delete operator
Verifique se não há pods restantes nos namespaces da Apigee:
kubectl get pods -n apigeekubectl get pods -n apigee-system
Set the context to other existing regions and make sure the cassandra datacenter is removed
from the existing ring. The output should not show the removed data center details.
[[["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-28 UTC."],[[["\u003cp\u003eThis guide provides step-by-step instructions for decommissioning a region within a multi-region environment, beginning by ensuring no live traffic is routed to the region.\u003c/p\u003e\n"],["\u003cp\u003eThe process involves setting the Kubernetes context to the target region, validating the status of pods and components, and confirming the readiness of the Cassandra cluster.\u003c/p\u003e\n"],["\u003cp\u003eThe guide details how to delete Apigee instance components one by one using Helm delete commands, specifying the importance of using the correct release names for the components.\u003c/p\u003e\n"],["\u003cp\u003eAfter deleting the components, it is necessary to verify the absence of any remaining pods within the Apigee namespaces.\u003c/p\u003e\n"],["\u003cp\u003eThe final steps include setting the context to other regions and checking that the removed data center is also no longer showing up as part of the remaining Cassandra cluster.\u003c/p\u003e\n"]]],[],null,["# Decommission a hybrid region\n\n| You are currently viewing version 1.12 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\n\nThis guide explains the procedure to decommission a region in a multi region environment.\n| Please ensure there is no live traffic going to the region you plan to delete.\n\nDecommission a hybrid region\n----------------------------\n\n1. Set the kubernetes contexts to the region that needs to be decommissioned.\n List your current contexts to see the context name for each cluster:\n\n ```\n kubectl config get-contexts\n ```\n\n\n Set the context to the cluster and region you want to decommission: \n\n ```\n kubectl config use-context CONTEXT_NAME\n ```\n\n\n Where \u003cvar translate=\"no\"\u003eCONTEXT_NAME\u003c/var\u003e is the context name for the cluster and region.\n\n\n For example: \n\n kubectl config get-contexts\n CURRENT NAME CLUSTER AUTHINFO NAMESPACE\n gke_example-org-1_us-central1_example-cluster-1 gke_example-org-1_us-central1_example-cluster-1 gke_example-org-1_us-central1_example-cluster-1 apigee\n * gke_example-org-1_us-central1_example-cluster-2 gke_example-org-1_us-central1_example-cluster-2 gke_example-org-1_us-central1_example-cluster-2 apigee\n gke_example-org-1_us-west1_example-cluster-2 gke_example-org-1_us-west1_example-cluster-2 gke_example-org-1_us-west1_example-cluster-2 apigee\n\n kubectl config use-context gke_example-org-1_us-west1_example-cluster-2\n\n2. Validate all the pods in the region are in a running or completed state: \n\n ```\n kubectl get pods -n apigee\n ``` \n\n ```\n kubectl get pods -n apigee-system\n ```\n3. Validate the release of components using helm: \n\n ```\n helm -n apigee list\n ``` \n\n ```\n helm -n apigee-system list\n ```\n\n For example: \n\n helm -n apigee list\n NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION\n datastore apigee 2 2024-03-29 17:08:07.917848253 +0000 UTC\tdeployed apigee-datastore-1.12.0 1.12.0\n ingress-manager apigee 2 2024-03-29 17:21:02.917333616 +0000 UTC\tdeployed apigee-ingress-manager-1.12.0 1.12.0\n redis apigee 2 2024-03-29 17:19:51.143728084 +0000 UTC\tdeployed apigee-redis-1.12.0 1.12.0\n telemetry apigee 2 2024-03-29 17:16:09.883885403 +0000 UTC\tdeployed apigee-telemetry-1.12.0 1.12.0\n exampleor apigee 2 2024-03-29 17:21:50.899855344 +0000 UTC\tdeployed apigee-org-1.12.0 1.12.0\n\n4. Validate the status of the Cassandra cluster. List the cassandra pods:\n\n ```\n kubectl get pods -n APIGEE_NAMESPACE -l app=apigee-cassandra\n ```\n\n For example: \n\n kubectl get pods -n apigee -l app=apigee-cassandra\n NAME READY STATUS RESTARTS AGE\n apigee-cassandra-default-0 1/1 Running 0 2h\n apigee-cassandra-default-1 1/1 Running 0 2h\n apigee-cassandra-default-2 1/1 Running 0 2h\n apigee-cassandra-default-3 1/1 Running 0 16m\n apigee-cassandra-default-4 1/1 Running 0 14m\n apigee-cassandra-default-5 1/1 Running 0 13m\n apigee-cassandra-default-6 1/1 Running 0 9m\n apigee-cassandra-default-7 1/1 Running 0 9m\n apigee-cassandra-default-8 1/1 Running 0 8m\n\n5. Delete the Apigee instance in the context you just selected: Delete the components one at a time.\n\n | **Note:** In the following `helm delete` commands, the names given for the compnents are the release names, the names specified for the component when they were installed. For example, if you installed the datastore component with the helm command `helm install `**datastore**` apigee-datastore`, the release name for the component is `datastore`. If you used different release names when installing the components, specify those names when deleting them.\n |\n |\n For example: `helm -n `\u003cvar translate=\"no\"\u003eapigee\u003c/var\u003e` delete my-datastore-region-1` \n\n ```\n helm -n apigee delete datastore\n ``` \n\n ```\n helm -n apigee delete telemetry\n ``` \n\n ```\n helm -n apigee delete ingress-manager\n ``` \n\n ```\n helm -n apigee delete redis\n ``` \n\n ```\n helm -n apigee delete ORG_NAME\n ```\n\n Repeat the following command for every environment: \n\n ```\n helm -n apigee delete ENV_NAME\n ```\n\n Repeat the following command for every environment group: \n\n ```\n helm -n apigee delete ENV_GROUP_NAME\n ``` \n\n ```\n helm -n apigee-system delete operator\n ```\n6. Verify there are no pods remaining in the Apigee namespaces: \n\n kubectl get pods -n apigee\n kubectl get pods -n apigee-system\n\n7. Set the context to other existing regions and make sure the cassandra datacenter is removed from the existing ring. The output should not show the removed data center details.\n\n ```\n kubectl exec apigee-cassandra-default-0 -n apigee -- nodetool -u JMX_USER -pw JMX_PASSWORD status\n ```\n| **Note:** If the entries of the deleted datacenter are still present in the Cassandra **nodetool** output, see [Stale references to deleted secondary region pods in Cassandra cluster](../../api-platform/troubleshoot/playbooks/cassandra/cassandra-pods-not-starting-secondary-region#stale-ref-deleted-region)."]]
