In Apigee hybrid , can we expand the Cassandra ring based on below scenario ?
Eg: Already have Apigee hybrid runtime in Apigee Org -A connected to Management plane running in Azure AKS Cluster.
Later I want to add GKE Apigee hybrid runtime, which is in different cluster with its own management plane, which is in Apigee Org -B of GKE to above Azure AKS Cassandra as a new Cassandra Ring (after X weeks) referring to Org A (To Azure-AKS-Apigee runtime in Apigee Org A) . Hence Cassandra Ring between Org-A and Org-B
Later I want to add On premise Apigee hybrid runtime (Cassandra Ring ) which is in a different cluster with its own management plane, which was in Apigee Org C to above Cassandra Ring (To Azure-AKS-Apigee runtime Org A) after another Y weeks. Then results in Cassandra Ring between Org-A , Org-B and Org-C
Note: Azure AKS Apigee hybrid and GKE Apigee hybrid and on premise Apigee hybrid are in different clusters and in diff Org.
Will maintain same version and required Apigee Cassandra perquisites including port opening and other details as indicated in
Expanding Apigee to multiple regions | Google Cloud Lists Region expansion
Multi-region deployment | Apigee | Google Cloud Apigee hybrid Cassandra Multi region
https://cloud.google.com/apigee/docs/hybrid/v1.9/ports - Ports for hybrid
Trying to understand, such Cassandra RING expansion will have any impact ?
Initially GKE Apigee hybrid runtime & On premise Apigee hybrid runtime will be in different Apigee Org and with its own management plane, will join Azure AKS Cluster Apigee hybrid Org and will plan expansion of Cassandra Ring with the Apigee org and management plane (of Azure AKS) which . Azure AKS Cluster contains.
Q: Do we have any similar doc to follow for such cases, to cover such Cassandra ring expansion ?
Q: Does such plan go good for production ? without down time ..
One way is to have all three Apigee Hybrid Cassandra ring expansion on day 1 with single Management plane. But above is different Cassandra Ring expansion scenario, hence trying to understand any best practices.