b06a7ea554
Vagrantfile: setup proxy inside virtual machines In corporate networks, it is good to pre-configure proxy variables. Reload docker.socket after installing flannel on coreos Workaround for #569 Swap order in which we reload docker/socket Update README.md Add new var skip_dnsmasq_k8s If skip_dnsmasq is set, it will still not set up dnsmasq k8s pod. This enables independent setup of resolvconf section before kubelet is up. Use tar+register instead of copy/slurp for distributing tokens and certs Related bug: https://github.com/ansible/ansible/issues/15405 Uses tar and register because synchronize module cannot sudo on the remote side correctly and copy is too slow. This patch dramatically cuts down the number of tasks to process for cert synchronization. Update OWNERS Add CI test layouts * Drop Wily from test matrix * Replace the Wily cases dropped with extra cases to test separate roles deployment Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com> Adds functionality to have masters and nodes with no floating IP. Updates ansible group vars on terraform/openstack to follow the inventory/group_vars/all.yml file. Vagrantfile: use Ubuntu 16.04 LTS Use recent supported version of Ubuntu for local development setup with Vagrant. Vagrantfile: setup proxy inside virtual machines In corporate networks, it is good to pre-configure proxy variables. Reload docker.socket after installing flannel on coreos Workaround for #569 Swap order in which we reload docker/socket Update README.md |
||
|---|---|---|
| contrib/terraform | ||
| docs | ||
| inventory | ||
| roles | ||
| scripts | ||
| tests | ||
| .gitignore | ||
| .gitmodules | ||
| .travis.yml | ||
| ansible.cfg | ||
| cluster.yml | ||
| code-of-conduct.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| OWNERS | ||
| README.md | ||
| RELEASE.md | ||
| requirements.txt | ||
| requirements.yml | ||
| ubuntu-bootstrap.yml | ||
| uploads.yml | ||
| Vagrantfile | ||
##Deploy a production ready kubernetes cluster
If you have questions, you can invite yourself to chat with us on Slack! 
- Can be deployed on AWS, GCE, 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 (deprecated, a newer go version soon)
Ansible usual commands
vagrant by simply running vagrant up (for tests purposes)
- Requirements
- Getting started
- Vagrant install
- CoreOS bootstrap
- Ansible variables
- Cloud providers
- OpenStack
- AWS
- Network plugins
- Roadmap
Supported Linux distributions
- CoreOS
- Debian Wheezy, Jessie
- Ubuntu 14.10, 15.04, 15.10, 16.04
- Fedora 23
- CentOS/RHEL 7
Versions
kubernetes v1.4.3
etcd v3.0.1
flanneld v0.6.2
calicoctl v0.22.0
weave v1.6.1
docker v1.10.3
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
- Copy your ssh keys to all the servers part of your inventory.
- Ansible v2.x and python-netaddr
Network plugins
You can choose between 3 network plugins. (default: flannel with vxlan backend)
-
flannel: gre/vxlan (layer 2) networking.
-
calico: bgp (layer 3) networking.
-
weave: Weave is a lightweight container overlay network that doesn't require an external K/V database cluster.
(Please refer toweavetroubleshooting documentation)
The choice is defined with the variable kube_network_plugin
CI Tests
Google Compute Engine
| Calico | Flannel | Weave |
------------- | ------------- | ------------- | ------------- |
Ubuntu Xenial ||
|
|
CentOS 7 |
|
|
|
CoreOS (stable) |
|
|
|
CI tests sponsored by Google (GCE), and teuto.net for OpenStack.