NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
cassandra-data-apigee-cassandra-default-0 Bound pvc-92234ba7-941b-4dab-82c6-8a5288a2c8d4 100Gi RWO standard 21m
cassandra-data-apigee-cassandra-default-1 Bound pvc-6be911fc-91f7-465d-a02e-933428ee10b2 100Gi RWO standard 20m
cassandra-data-apigee-cassandra-default-2 Bound pvc-14ba34e4-fd5c-4d59-8413-a331dcad3404 100Gi RWO standard 19m
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-07-10 (世界標準時間)。"],[[["This documentation outlines how to expand the persistent volumes used by the Apigee hybrid Cassandra database to accommodate increasing storage needs without adding new nodes, since the initial persistent volume size is immutable."],["The process involves directly editing the Persistent Volume Claim (PVC) to increase the volume size, however only Kubernetes storage classes that support Persistent Volume expansion are compatible with this process."],["After updating the volume size in the PVC, users must back up, delete, and recreate the statefulset with the new storage size, ensuring the updated size matches the `overrides.yaml` file configuration."],["Once the statefulset has been re-created, the `overrides.yaml` file needs to be updated, then the new configuration applied to the cluster and finally users should verify that all the pods and statefulsets have updated to the new storage size."],["The end of life status of version 1.8 of Apigee hybrid documentation indicates that users should upgrade to a newer, supported version of Apigee, further information on versions can be found through the provided link."]]],[]]