Bogdan Dobrelya 365ecdcd6d Update docs

Link docs to README, update README with recent info.
Update comparsions, add kubeadm vs kargo.
Better describe variables precedence UX impact.

Signed-off-by: Bogdan Dobrelya <bogdando@mail.ru>

2017-01-09 16:32:55 +01:00

4.1 KiB

Raw Blame History

##Deploy a production ready kubernetes cluster

If you have questions, join us on the kubernetes slack, channel #kargo.

Can be deployed on AWS, GCE, Azure, OpenStack or Baremetal
High available cluster
Composable (Choice of the network plugin for instance)
Support most popular Linux distributions
Continuous integration tests

To deploy the cluster you can use :

kargo-cli
Ansible usual commands and inventory builder
vagrant by simply running vagrant up (for tests purposes)

Supported Linux distributions

Container Linux by CoreOS
Debian Jessie
Ubuntu 16.04
CentOS/RHEL 7

Note: Upstart/SysV init based OS types are not supported.

Versions of supported components

kubernetes v1.5.1
etcd v3.0.6
flanneld v0.6.2
calicoctl v0.23.0
canal (given calico/flannel versions)
weave v1.6.1
docker v1.12.5
rkt v1.21.0

Note: rkt support as docker alternative is limited to control plane (etcd and kubelet). Docker is still used for Kubernetes cluster workloads and network plugins' related OS services. Also note, only one of the supported network plugins can be deployed for a given single cluster.

Requirements

The target servers must have access to the Internet in order to pull docker images.
The firewalls are not managed, you'll need to implement your own rules the way you used to. in order to avoid any issue during deployment you should disable your firewall.
The target servers are configured to allow IPv4 forwarding.
Copy your ssh keys to all the servers part of your inventory.
Ansible v2.2 (or newer) and python-netaddr

Network plugins

You can choose between 4 network plugins. (default: flannel with vxlan backend)

flannel: gre/vxlan (layer 2) networking.
calico: bgp (layer 3) networking.
canal: a composition of calico and flannel plugins.
weave: Weave is a lightweight container overlay network that doesn't require an external K/V database cluster.
(Please refer to weave troubleshooting documentation).

The choice is defined with the variable kube_network_plugin. There is also an option to leverage built-in cloud provider networking instead. See also Network checker.

CI Tests

CI/end-to-end tests sponsored by Google (GCE), and teuto.net for OpenStack. See the test matrix for details.