We are configuring etcd2 but starting the old etcd service. This will work on a single machine but isn't the user's intention. This is untested, I just wanted to fix it first.
I re-used setup-network-environment instead of $private_ipv4, this
does meant overwriting the docker.service with a custom service.
Also, the wget command was always getting kube-register, curl
works more reliabily for this.
- allow payloads to run in privileged mode.
- update kube-register to latest upstream (v0.0.3).
- jump into the etcd2 bandwagon.
- etcd master on master node.
- etcd proxies in nodes.
- update docs to reflect minimum required CoreOS version.
- 653.0.0 is the first to ship with etcd2, which we now consume.
- propagate changes on coreos/cloud-configs/ also to aws/cloud-configs/.
- update tested k8s versions that this addresses in the
getting-started-guides table ence making sure we are consistent across
it regarding the versions we claim to have tested, add myself there as
contact too.
- do not assume that cloud-init shortcuts will get everything right.
- they won't (as setup-network-environment who populates *_ipv4, etc
only runs way later).
- use flannel's plain defaults, as they should just be enough for the
common case.
Signed-off-by: António Meireles <antonio.meireles@reformi.st>
given that etcd is disabled in the nodes we need to wait for master's etcd to be
available so that flanneld gets properly wired.
Signed-off-by: António Meireles <antonio.meireles@reformi.st>
avoids race conditions (docker/docker-registry#892) when multiple workers are
attempting to run sql migrations simultaneously. dunno why this isn't the
registry's default since this isn't specially hard to trigger so we're just
playing safe here.
Signed-off-by: António Meireles <antonio.meireles@reformi.st>
in the footsteps of #5254 merge earlier today and per @brendandburns comments
in the PR review thread...
Signed-off-by: António Meireles <antonio.meireles@reformi.st>
a more idiomatic take on #4378. as a bonus, and to be nice on
resources, an ultra lightweight docker-registry container is
consumed.
Signed-off-by: António Meireles <antonio.meireles@reformi.st>
Update node.yaml to support graphdriver: overlay as btrfs produces "fatal" "prerequisites for driver not satisfied (wrong filesystem?)" on CoreOS Alpha 561.0.0
k8s-merge-robot