Comments (7)
@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.
from kubestack.
@kelseyhightower I'm not sure that is a good idea.
From my experience when you have something bad going on in the zone, your whole cluster
stops working.
Also then you have no HA for you etcd cluster and your nodes.
Specially if you want to run more than one k8s pod for some website .
Plus it makes more expensive when you have more 3x etcd/ k8s master servers sets
and so on.
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.
from kubestack.
@kelseyhightower We might have zones listed in variables.tf
e.g.:
variable "zone1" {
default = "us-central1-a"
}
variable "zone2" {
default = "us-central1-b"
}
or terraform.tfvars
(I'm new to terraform)
and then have zone1.tf and etc files with the worker_count or something like that
from kubestack.
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.
from kubestack.
I have no problems running coreos and kubernetes clusters spread around different zones in the same region.
A couple time one of zones had issues, nothing was working there, but that did not affect my setup much.
Not sure that it is the 'best practice' to run cluster per zone.
from kubestack.
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.
from kubestack.
I think I got an idea about multi zones setup.
Running etcd clusters on GCE no timeouts adjustments are needed. but Aws multi zone network latency is much worse, had many issues there. happy with my move to GCE
from kubestack.
Related Issues (11)
- Don't hardcode FQDN in systemd unit files HOT 1
- kubestack systemd units update HOT 4
- support for different sizes of etcd clusters HOT 2
- setup more clusters on the same project HOT 2
- coreos update HOT 1
- fleet and metadata support HOT 1
- Missing kubestack.tar.gz HOT 2
- bootstrap mixed GCE and bare-metal cluster HOT 4
- change where kubestack-account.json file gets stored HOT 5
- kubestack binaries update HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kubestack.