- 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>
# *** ERROR: *** docs are out of sync between cli and markdown
# run hack/run-gendocs.sh > docs/kubectl.md to regenerate
#
# Your commit will be aborted unless you regenerate docs.
COMMIT_BLOCKED_ON_GENDOCS
# *** ERROR: *** docs are out of sync between cli and markdown
# run hack/run-gendocs.sh > docs/kubectl.md to regenerate
#
# Your commit will be aborted unless you regenerate docs.
COMMIT_BLOCKED_ON_GENDOCS
Refactored the Juju getting started guide with @erictune and
@brendandburns reccomendations on having a supported matrix listing
under the cloud support header.
libvirt-coreos is a cluster provider for kubernetes that starts local VMs and
runs kubernetes on it.
Its goal is to provide a multi-machines environment to develop and test kubernetes.
The purpose is mostly the same as the vagrant provider but with a big focus on
efficiency. The vagrant cluster takes a long time to boot and consumes a huge
amount of disk space. libvirt-coreos aims at being cheaper. As a consequence,
libvirt-coreos allows to start bigger clusters with more minions than vagrant.