Decommission a hybrid region

Version 1.16 (latest)keyboard_arrow_down

This guide explains the procedure to decommission a region in a multi region environment.

Decommission a hybrid region

Set the kubernetes contexts to the region that needs to be decommissioned.

List your current contexts to see the context name for each cluster:

kubectl config get-contexts

Set the context to the cluster and region you want to decommission:

kubectl config use-context CONTEXT_NAME

Where CONTEXT_NAME is the context name for the cluster and region.

For example:

kubectl config get-contexts
  CURRENT  NAME                                                CLUSTER                                             AUTHINFO                                           NAMESPACE
           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
  *        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
           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

kubectl config use-context gke_example-org-1_us-west1_example-cluster-2

Validate all the pods in the region are in a running or completed state:
```
kubectl get pods -n APIGEE_NAMESPACE
```
Note: You can use any namespace. apigee is the default namespace. Be sure to replace APIGEE_NAMESPACE with the name of your namespace in the following commands.

Validate the release of components using helm:

helm -n APIGEE_NAMESPACE list

For example:

helm -n apigee list
  NAME              NAMESPACE REVISION  UPDATED                                 STATUS    CHART                         APP VERSION
  datastore         apigee    2         2024-03-29 17:08:07.917848253 +0000 UTC	deployed  apigee-datastore-1.12.0       1.12.0
  ingress-manager   apigee    2         2024-03-29 17:21:02.917333616 +0000 UTC	deployed  apigee-ingress-manager-1.12.0 1.12.0
  redis             apigee    2         2024-03-29 17:19:51.143728084 +0000 UTC	deployed  apigee-redis-1.12.0           1.12.0
  telemetry         apigee    2         2024-03-29 17:16:09.883885403 +0000 UTC	deployed  apigee-telemetry-1.12.0       1.12.0
  exampleor         apigee    2         2024-03-29 17:21:50.899855344 +0000 UTC	deployed  apigee-org-1.12.0             1.12.0

Validate the status of the Cassandra cluster.

List the cassandra pods:

kubectl get pods -n APIGEE_NAMESPACE -l app=apigee-cassandra

For example:

kubectl get pods -n apigee -l app=apigee-cassandra
  NAME                          READY    STATUS     RESTARTS    AGE
  apigee-cassandra-default-0    1/1      Running    0           2h
  apigee-cassandra-default-1    1/1      Running    0           2h
  apigee-cassandra-default-2    1/1      Running    0           2h
  apigee-cassandra-default-3    1/1      Running    0           16m
  apigee-cassandra-default-4    1/1      Running    0           14m
  apigee-cassandra-default-5    1/1      Running    0           13m
  apigee-cassandra-default-6    1/1      Running    0           9m
  apigee-cassandra-default-7    1/1      Running    0           9m
  apigee-cassandra-default-8    1/1      Running    0           8m

Delete the Apigee instance in the context you just selected:
Delete the components one at a time.

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.
For example: helm -n APIGEE_NAMESPACE delete my-datastore-region-1
```
helm -n APIGEE_NAMESPACE delete datastore
```
```
helm -n APIGEE_NAMESPACE delete telemetry
```
```
helm -n APIGEE_NAMESPACE delete ingress-manager
```
```
helm -n APIGEE_NAMESPACE delete redis
```
```
helm -n APIGEE_NAMESPACE delete ORG_NAME
```
Repeat the following command for every environment:
```
helm -n APIGEE_NAMESPACE delete ENV_RELEASE_NAME
```
Repeat the following command for every environment group:
```
helm -n APIGEE_NAMESPACE delete ENV_GROUP_RELEASE_NAME
```
```
helm -n APIGEE_NAMESPACE delete operator
```
ENV_RELEASE_NAME and ENV_GROUP_RELEASE_NAME are names used to keep track of installation and upgrades of the apigee-env and apigee-virtualhost charts. Helm release names must be unique within your Apigee hybrid installation. If your environment name is unique, this can be the same as ENV_NAME. However, if you have the same name for your environment and environment group, make sure to enter a unique Helm release name for each. For example, if both are named dev you could use something like dev-env-release and dev-envgroup-release.

You can see a list of release names with the helm list command:
```
helm list -n APIGEE_NAMESPACE
```
.
Verify there are no pods remaining in the Apigee namespaces:
```
kubectl get pods -n APIGEE_NAMESPACE
```
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.
```
kubectl exec apigee-cassandra-default-0 -n APIGEE_NAMESPACE  -- nodetool -u JMX_USER -pw JMX_PASSWORD status
```

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

Last updated 2026-07-23 UTC.

Decommission a hybrid region Stay organized with collections Save and categorize content based on your preferences.

Decommission a hybrid region

Decommission a hybrid region