Skip to content
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

Create working setup for Kubernetes #40

Open
vniche opened this issue Jul 11, 2020 · 3 comments
Open

Create working setup for Kubernetes #40

vniche opened this issue Jul 11, 2020 · 3 comments

Comments

@vniche
Copy link
Contributor

vniche commented Jul 11, 2020

I will start soon working again on a working cete cluster on Kubernetes and was wondering if anyone here already achieved something of a sort 🤔

@mosuka
Copy link
Owner

mosuka commented Jul 14, 2020

I'd like to run a Cete cluster on Kubernetes, but I haven't started anything yet.

@xaocon
Copy link

xaocon commented Aug 12, 2020

Just started looking at the project. Sounds pretty neat. I have some helm experience and could make something that would make deployment pretty easy but I don't really understand the requirements yet. What state information do nodes need to join a cluster? Seems like maybe you just need one up and then the rest get --peer-grpc-address with the address of the "leader"? Everything else looks like it's pretty standard across each node except for some concept of ID which I think just needs to be different for each node in the cluster?

@vniche
Copy link
Contributor Author

vniche commented Aug 14, 2020

I've tried a few setups myself @xaocon, i guess the current implementation does not provide a way to let raft itself elect the leader but only to use a previously chosen one (as you mentioned with --peer-grpc-address), for a initial version you could try working with an OrderedReady StatefulSet, pointing to the first node as the leader.

Maybe we could fetch a few ideas from:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants