Delete the Apigee instance in the context you just selected with the apigeectl
command:
Apigeectl delete --all -f overrides.yaml
Verify there are no pods remaining in the Apigee namespaces:
kubectl get pods -n apigee
kubectl get pods -n apigee-systemkubectl get pods -n cert-manager
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eThis document guides you through the process of decommissioning a region in an Apigee hybrid multi-region environment.\u003c/p\u003e\n"],["\u003cp\u003eBefore starting, ensure that no live traffic is directed to the region you intend to decommission.\u003c/p\u003e\n"],["\u003cp\u003eThe process involves setting the Kubernetes context to the region being decommissioned, and then deleting the Apigee instance in that context using the \u003ccode\u003eapigeectl\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eAfter deletion, it is important to verify that no pods remain in the Apigee namespaces and that the Cassandra datacenter for the decommissioned region has been removed from the existing ring.\u003c/p\u003e\n"],["\u003cp\u003eNote that if stale references of the decommissioned region still appear in the Cassandra nodetool output, there are steps that need to be followed, that are linked in the documentation.\u003c/p\u003e\n"]]],[],null,["# Decommission a hybrid region\n\n| You are currently viewing version 1.9 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. Delete the Apigee instance in the context you just selected with the `apigeectl` command: \n\n ```\n Apigeectl delete --all -f overrides.yaml\n ```\n3. 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 kubectl get pods -n cert-manager\n\n4. 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)."]]