-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
K8SSAND-59 ⁃ How to get multi DC environment created? #566
Comments
|
k8ssandra does not yet support multi-DC clusters. See #524. Note that cass-operator does however already have support for multi-DC. It just is not yet exposed in k8ssandra. |
|
Thanks for revert. Do we know how soon we can get this feature included? Cassandra with single DC is not a production choice for most of the people. What we can do to priorities this? |
|
Great questions 😄
My personal preference would be to address this in 2.0. The short version is, I don't want to implement multi-DC support in the Helm charts. See #485 for some background.
Comment on and up vote #524. More generally speaking the more involved you can be with the project the better! In terms of multi-DC support, I think of two high level scenarios - 1) DCs running in the same k8s cluster and 2) DCs running in different k8s clusters. Do you have more interest in one of those scenarios? |
|
Can we go ahead and close this? |
|
With #548 you can set up multiple DCs running in different k8s clusters. There are a couple caveats though. First, pods in both clusters need to be reachable by their IP addresses. Secondly, there is no centralized installation, configuration, management. You will need to run |
Type of question
How to perform a particular operation
What did you do?
Tried to spin up K8ssandra 2 DC with 3 node in each.
helm install -f k8ssandra.yaml k8ssandra k8ssandra/k8ssandraAbove command only create
k8s-dc1DC and corresponding pods for 3 nodes.Did you expect to see some different?
I would expect 2 DC to be created with 3 node in each DC.
Environment
DEV
k8ssandra-1.0.0┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: K8SSAND-59
┆priority: Medium
The text was updated successfully, but these errors were encountered: