-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Any examples of this working in a k8s environment? #93
Comments
Yes, mnesiac should work in kubernetes though I don't have an example readily available, apologies. Might be good to get something added to the docs about it at some point though. |
I've tried to use disc_only copies with multiple pods, the problem is that each pod has its own unique hostname, and it ends up creating ghost mnesia copies that ends up blocking other new pods rolling out I'll try to use a statefulset to keep the hostname predictable across multiple pods. I'll keep adding here what I can find for those who want to use disc only copies with k8s |
Any news on this? Working examples? |
I've managed to write an example here: https://github.com/eliasdarruda/mnesia-with-k8s This is a working version using Mnesiac and kubernetes with StatefulSet, this is saving and recovering the state correctly on rollouts and new setups. |
@eliasdarruda Thank you very much for sharing. |
Question
I'm wondering how would it work in a k8s environment with a multi node or single node volume.
Does anyone have a working example already?
The text was updated successfully, but these errors were encountered: