This process allows you to expand the persistent volumes used by the Apigee hybrid Cassandra
database to accommodate greater storage needs without needing to create new nodes just to provide
more storage.
Overview
The Apigee hybrid cassandra component uses persistent volumes
to store data. Persistent volume size is defined during installation and initial configuration. This initial
storage size is an immutable value and cannot be changed. Therefore, any new node added to the cluster
will use the same persistent volume size.
It is possible to increase the size of the existing persistent volume by making the changes directly on
the Persistent volume Claim. New nodes will still use the smaller initial persistent volume size.
If your hybrid Cassandra database is nearing its storage capacity, you can use this procedure
to expand the existing persistent volumes and allow new nodes to expand their persistent volumes as
well.
Expand Cassandra persistent volumes
Update the volume size to the desired size:
kubectl -n apigee edit pvc
Check the updated volume capacity:
kubectl get pvc -n apigee
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
cassandra-data-apigee-cassandra-default-0 Bound pvc-92234ba7-941b-4dab-82c6-8a5288a2c8d4 500Gi RWO standard 21m
cassandra-data-apigee-cassandra-default-1 Bound pvc-6be911fc-91f7-465d-a02e-933428ee10b2 500Gi RWO standard 20m
cassandra-data-apigee-cassandra-default-2 Bound pvc-14ba34e4-fd5c-4d59-8413-a331dcad3404 500Gi RWO standard 19m
Backup, delete and recreate the statefulset with the new storage size. The following commands
creates a configuration file apigee-cassandra-default.yaml you can use to capture
the current Cassandra configuration. You then modify and apply this configuration:
kubectl -n apigee get sts apigee-cassandra-default -o yaml > apigee-cassandra-default.yaml
Update the storage size in the apigee-cassandra-default.yaml file with the new
storage size. This must match the size you intend to apply in your overrides.yaml.
For example:
resources:
requests:
storage: 500Gi
Re-apply the statefulset configuration with the updated storage size:
kubectl apply -f apigee-cassandra-default.yaml
Verify that statefulset was re-created correctly:
kubectl get sts -n apigee
Your output should look something like:
NAME READY AGE
apigee-cassandra-default 3/3 6m56s
Update the your overrides file with new volume size that you specified when you edited the pvc:
[[["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-26 UTC."],[],[],null,["| 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\nThis process allows you to expand the persistent volumes used by the Apigee hybrid Cassandra\ndatabase to accommodate greater storage needs without needing to create new nodes just to provide\nmore storage.\n\nOverview\n\nThe Apigee hybrid `cassandra` component uses persistent volumes\nto store data. Persistent volume size is defined during installation and initial configuration. This initial\nstorage size is an immutable value and cannot be changed. Therefore, any new node added to the cluster\nwill use the same persistent volume size.\n\nIt is possible to increase the size of the existing persistent volume by making the changes directly on\nthe Persistent volume Claim. New nodes will still use the smaller initial persistent volume size.\n\nIf your hybrid Cassandra database is nearing its storage capacity, you can use this procedure\nto expand the existing persistent volumes and allow new nodes to expand their persistent volumes as\nwell.\n| **Note:** This process only applies to Kubernetes storage classes that support PersistentVolume expansion. See the **[Allow\n| Volume Expansion list](https://kubernetes.io/docs/concepts/storage/storage-classes/#allow-volume-expansion)** in the Kubernetes documentation.\n|\n|\n| If you do not know what storage class your hybrid installation uses, you can check with\n| the following command. \n|\n| ```\n| kubectl -n apigee get sc standard -o json | grep 'provisioner'\n| ```\n|\n|\n| The output will look something like: \n|\n| ```text\n| \"provisioner\": \"kubernetes.io/gce-pd\",\n| ```\n|\n|\n| Where `gce-pd` is an abbreviation for the *gcePersistentDisk* storage class.\n| You can find a list of storage class abbreviations in the **[Parameters\n| list](https://kubernetes.io/docs/concepts/storage/storage-classes/#parameters)** in the Kubernetes documentation.\n\nExpand Cassandra persistent volumes\n\n1. Update the volume size to the desired size: \n\n ```\n kubectl -n apigee edit pvc\n ```\n2. Check the updated volume capacity: \n\n ```\n kubectl get pvc -n apigee\n ``` \n\n ```\n NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE\n cassandra-data-apigee-cassandra-default-0 Bound pvc-92234ba7-941b-4dab-82c6-8a5288a2c8d4 500Gi RWO standard 21m\n cassandra-data-apigee-cassandra-default-1 Bound pvc-6be911fc-91f7-465d-a02e-933428ee10b2 500Gi RWO standard 20m\n cassandra-data-apigee-cassandra-default-2 Bound pvc-14ba34e4-fd5c-4d59-8413-a331dcad3404 500Gi RWO standard 19m\n ```\n3. Backup, delete and recreate the statefulset with the new storage size. The following commands creates a configuration file `apigee-cassandra-default.yaml` you can use to capture the current Cassandra configuration. You then modify and apply this configuration:\n 1.\n\n ```\n kubectl -n apigee get sts apigee-cassandra-default -o yaml \u003e apigee-cassandra-default.yaml\n ```\n 2.\n\n ```\n kubectl -n apigee delete sts --cascade=orphan apigee-cassandra-default\n ```\n 3. Check that the `delete` operation is complete: \n\n ```\n kubectl get sts -n apigee\n ```\n\n\n Your output should look like: \n\n ```text\n No resources found in apigee namespace.\n ```\n 4. Update the storage size in the `apigee-cassandra-default.yaml` file with the new storage size. This must match the size you intend to apply in your `overrides.yaml`. For example: \n\n ```text\n resources:\n requests:\n storage: 500Gi\n ```\n 5. Re-apply the statefulset configuration with the updated storage size: \n\n ```\n kubectl apply -f apigee-cassandra-default.yaml\n ```\n 6. Verify that statefulset was re-created correctly: \n\n ```\n kubectl get sts -n apigee\n ```\n\n\n Your output should look something like: \n\n ```text\n NAME READY AGE\n apigee-cassandra-default 3/3 6m56s\n ```\n4. Update the your overrides file with new volume size that you specified when you edited the pvc: \n\n ```actionscript-3\n cassandra:\n storage:\n storageSize: 500Gi\n ```\n5. See [`cassandra.storage.capacity`](/apigee/docs/hybrid/v1.12/config-prop-ref#cassandra-storage-capacity) for more details.\n6. Apply the updated configuration to the cluster: \n\n ```\n helm upgrade datastore apigee-datastore/ \\\n --namespace apigee \\\n --atomic \\\n -f OVERRIDES_FILE.yaml\n ```\n | **Note:** If you see an error saying `Error: UPGRADE FAILED: \"datastore\" has no deployed releases`, replace `upgrade` with `install` and try the command again.\n7. Check if the newly created sts has the updated storage size: \n\n ```\n kubectl get sts -n apigee apigee-cassandra -o yaml |grep storage\n ``` \n\n ```\n storage: 500Gi\n ```\n8.\n Check if C\\* pods data volume got updated with new size:\n\n ```\n kubectl exec -n apigee -it apigee-cassandra-default-0 -- df -h|grep \"/opt/apigee/data\"\n ``` \n\n ```text\n /dev/sdb 99G 69M 99G 1% /opt/apigee/data\n ```"]]
