-
Notifications
You must be signed in to change notification settings - Fork 64
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
provision master and node between different zones #7
Comments
@rimusz What do you think about the idea of multiple clusters, one in each zone? Depending on the network boundaries between zones, it may offer a better experience to to have multiple clusters vs on big one. |
@kelseyhightower I'm not sure that is a good idea. Also then you have no HA for you etcd cluster and your nodes. Plus it makes more expensive when you have more 3x etcd/ k8s master servers sets So you end up with ubernetes federation even for the small e.g. 20 nodes clusters setup I never ever trust one zone setup, bad experience in the past. |
@kelseyhightower We might have zones listed in
or and then have zone1.tf and etc files with the worker_count or something like that |
The current "best practice" for cabernets seems to be to run a cluster per zone. The nodes chat with the master often, so they generally should be in the same failure domain. |
I have no problems running coreos and kubernetes clusters spread around different zones in the same region. Not sure that it is the 'best practice' to run cluster per zone. |
If you do multiple zones, for etcd, you need to use an odd number of zones to make sure a simple majority is maintained - also may need to adjust timeouts. I've only done this in AWS, however. |
I think I got an idea about multi zones setup. |
Would be good to provision master and node between different zones,
as to use one zone for the whole cluster is not a good idea.
For testing purposes it is fine, but people will start running production clusters :)
The text was updated successfully, but these errors were encountered: