-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
[Bug]: new node already at cluster Node is already a Storage Manager for different Cluster
#324
Comments
Are these nodes used earlier? You can remove |
@TristisOris I moved this bug to GitHub/kadalu/moana repo. Are you looking for Gluster alternative or curious about Kadalu Storage? |
no, all 3 nodes are fresh created vms. Not familiar with gluster too, but found that k8s drop it from support. |
|
Thanks for confirming. I will check it tomorrow and update here. |
Thanks. This project is not created to use with k8s. Please use https://github.com/kadalu/kadalu project if you are looking for k8s storage solution. Moana is for on-premise use cases without using k8s. Both these projects are based on core GlusterFS. |
ah, got it. Also we need some S3 not only for k8s, so i'll try both. |
Describe the bug
any attempts to create cluster not succeed.
same if use ns names (resolve via /etc/hosts conf)
To Reproduce
Steps to reproduce the behavior:
Actual behavior
here https://docs.kadalu.tech/kadalu-storage/latest/setup/ it say
No nodes are added to the cluster by default.
.info
config from nodes:{"pool_name":"","id":"0db99011-4883-494e-a6f5-fafc9c103530","name":"","token_hash":"","mgr_hostname":"","mgr_port":3000,"mgr_https":false,"mgr_token":"","joined":false}
So nodes really not at pool.
Environment:
ubuntu 22
Server Version : 1.2.0
CLI Version : 1.2.0
The text was updated successfully, but these errors were encountered: