-
Notifications
You must be signed in to change notification settings - Fork 298
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
Is this project still a PoC? Is it production ready? #109
Comments
To be honest, I haven‘t seen any progress on this for a while and I would not consider it to be production ready. I personally opted for kubeDB to set up a MongoDB cluster in Kubernetes |
Thank you @Maurice22 for your input 👍. I went trough the documentation for MySQL and MongoDB and looking for the replication and automatic failover topics, and as far as I understood it, it is working for a single cluster, but they doesn't seem to have options for a multi-zone or multi data center configuration. How many Data Center do you have in your config please? |
I'm running on a single data center so unfortunately I don't have any additional information for you here |
Okay, and what's your plan in the case that DC get down? |
Well, for now this is not our main concern.. However, as far as I understand it, if you have your kubernetes cluster span over multiple sites (i.e. having multiple kubernetes nodes), you don't need to care about it, as the replication and failover is handled by kubernetes itself. In the end, you can see kubernetes as abstraction from the physical hardware, taking care about cases where the hardware fails, I'd say |
Oh, unfortunately that's not an option because of physical constraints you'll get unstable network between the two sites, and you could end in a split brain issue or cluster freeze in the case masters are impacted. That's why Kube Federation V2 exists. |
If you'd like to know more about that topic, I recommend you to read that: https://www.percona.com/blog/2018/11/15/how-not-to-do-mysql-high-availability-geographic-node-distribution-with-galera-based-replication-misuse/ |
It is unfortunate that most documentation about mongodb and kubernetes uses this project to deploy the statefulset. |
@max-l-weaver - whats wrong with project. Just want to understand if you found anything here which might be of an issue. |
As a PoC for sidecars, it's perfect. As for getting an actual MongoDB replica set going, I initially had success, but as soon as I wanted to do anything more specific, the sidecars were breaking down easily. I recommend dropping this project for production. https://github.com/mongodb/mongodb-kubernetes-operator is new and prone to bugs as well, but it is a better alternative. |
This issue a little bit more specific than #97:
Is this project still a Proof Of Concept or is it production ready?
The text was updated successfully, but these errors were encountered: