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

Documentation on setting up a multi-cloud cluster? #219

Closed
zplizzi opened this issue Jul 29, 2021 · 4 comments
Closed

Documentation on setting up a multi-cloud cluster? #219

zplizzi opened this issue Jul 29, 2021 · 4 comments

Comments

@zplizzi
Copy link

zplizzi commented Jul 29, 2021

The docs clearly imply that one of the main uses of Kilo is setting up a multi-cloud cluster ("Kilo enables the operation of multi-cloud clusters"), but I can't anywhere find documentation of how to actually do that.

As an example, I have set up a cluster in EC2 using kubeadm with a single control plane node and a couple workers. Then I've started a GCP instance that I want to connect to the cluster using Kilo. How do I do this?? I can't find anywhere in the documentation that explains this step.

I know I can just open up my control plane node's IP and ports to the internet and let the GCP node connect directly with kubeadm join PUBLIC_IP:PORT - is that what I'm supposed to do? I'm not sure if that's safe to do. But in the kilo docs it says "The nodes in the mesh will require an open UDP port in order to communicate" - which I took to mean that there's a way to do this by only opening a single port that Kilo will use to make the connection for me somehow.

@zplizzi
Copy link
Author

zplizzi commented Jul 29, 2021

I know #165 is tracking requests for better documentation - just hoping maybe you can quickly point me in the right direction here :)

@zplizzi
Copy link
Author

zplizzi commented Jul 29, 2021

Ah, I just found #11, I think that has the explanation I was looking for. I'll try and close if successful :)

@leonnicolas
Copy link
Collaborator

Added this to #165

@zplizzi
Copy link
Author

zplizzi commented Jul 30, 2021

Didn't quite get this working, but the instructions in #11 definitely helped. It seems like kubeadm doesn't play super well with AWS EC2 nodes having different public vs private IPs.. had to do some hacky stuff to get that to work (to join a node from a different region that wasn't networked to the main cluster with VPC peering). Also couldn't get it to work with just kilo as the networking plugin - not sure what I was doing wrong there. Got farther when I used flannel and then put kilo on top of that. Unfortunately I had to stop working on this and shut down my test nodes so this will have to wait for another day. Looking forward to checking out the new documentation when it goes up :)

@zplizzi zplizzi closed this as completed Jul 30, 2021
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

2 participants