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

HA Kubernetes Setup #5

Open
capgadsx opened this issue Aug 31, 2017 · 5 comments
Open

HA Kubernetes Setup #5

capgadsx opened this issue Aug 31, 2017 · 5 comments

Comments

@capgadsx
Copy link
Member

capgadsx commented Aug 31, 2017

The idea is to implement the solution described in the official kubernetes documentation, using a clustered etcd deployment and load-balanced api-servers.
Clusterd Kubernetes

@mosoriob
Copy link
Contributor

Maybe this is a good start. kubernetes/kubeadm#277

@madiazp
Copy link
Contributor

madiazp commented Sep 11, 2017

We were thinking with @capgadsx that it will be a good solution to put kubemaster and etcd in a VM in Ovirt and do backups in lustre with rsync, so the HA is up to Ovirt. With a good VM configuration(auto net, auto service up in restarts, etc) the only enemy will be a IML server's failure or an entire datacenter failure.

@mosoriob
Copy link
Contributor

mosoriob commented Sep 11, 2017

That is overthink. 3 etcd is enough.

@maray
Copy link
Member

maray commented Sep 12, 2017

I agree with @sirspock. Please do not complicate things more than it will be needed. If 3 independent disks of 3 different servers fail at the same time, everyone will understand a 503!

@capgadsx can you edit your first comment to add a brief doc of the 3 etcd solution we are currently using? (just for the sake of documentation)

@capgadsx
Copy link
Member Author

At this point we already implemented the 3-member etcd cluster and we have 3 kubernetes api-servers running. We still have to setup the load-balancer for the api-servers

@capgadsx capgadsx changed the title HA for etcd (?) HA Kubernetes Setup Sep 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants