C12s/c12s-kubespray
3
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

update README with multi-master notes

Browse source
This commit is contained in:
Smaine Kahlouch 2015-12-13 16:59:22 +01:00
parent 9862afb097
commit f908309739
1 changed files with 24 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
README.md
View file

@ -6,8 +6,9 @@ Based on [CiscoCloud](https://github.com/CiscoCloud/kubernetes-ansible) work.
### Requirements ### Requirements
Tested on **Debian Jessie** and **Ubuntu** (14.10, 15.04, 15.10). Tested on **Debian Jessie** and **Ubuntu** (14.10, 15.04, 15.10).
The target servers must have access to the Internet in order to pull docker imaqes. * The target servers must have access to the Internet in order to pull docker imaqes.
The firewalls are not managed, you'll need to implement your own rules the way you used to. * The firewalls are not managed, you'll need to implement your own rules the way you used to.
* the following packages are required: openssl, curl, dnsmasq, python-httplib2 on remote servers and python-ipaddr on deployment machine.
Ansible v1.9.x Ansible v1.9.x
@ -21,7 +22,7 @@ Ansible v1.9.x
Quickstart Quickstart
------------------------- -------------------------
The following steps will quickly setup a kubernetes cluster with default configuration. The following steps will quickly setup a kubernetes cluster with default configuration.
These defaults are good for a test purposes. These defaults are good for tests purposes.
Edit the inventory according to the number of servers Edit the inventory according to the number of servers
``` ```
@ -45,6 +46,8 @@ Run the playbook
ansible-playbook -i environments/production/inventory cluster.yml -u root ansible-playbook -i environments/production/inventory cluster.yml -u root
``` ```
You can jump directly to "*Available apps, installation procedure*"
Ansible Ansible
------------------------- -------------------------
@ -111,20 +114,25 @@ loadbalancer_address="10.99.0.44"
roles: roles:
- { role: download, tags: download } - { role: download, tags: download }
- hosts: k8s-cluster # etcd must be running on master(s) before going on
- hosts: kube-master
roles: roles:
- { role: etcd, tags: etcd } - { role: etcd, tags: etcd }
- hosts: k8s-cluster
roles:
- { role: docker, tags: docker } - { role: docker, tags: docker }
- { role: network_plugin, tags: ['calico', 'flannel', 'network'] }
- { role: dnsmasq, tags: dnsmasq } - { role: dnsmasq, tags: dnsmasq }
- { role: network_plugin, tags: ['calico', 'flannel', 'network'] }
- hosts: kube-node
roles:
- { role: kubernetes/node, tags: node }
- hosts: kube-master - hosts: kube-master
roles: roles:
- { role: kubernetes/master, tags: master } - { role: kubernetes/master, tags: master }
- hosts: kube-node
roles:
- { role: kubernetes/node, tags: node }
``` ```
### Run ### Run
@ -136,6 +144,14 @@ ansible-playbook -i environments/dev/inventory cluster.yml -u root
Kubernetes Kubernetes
------------------------- -------------------------
### Multi master notes
* You can choose where to install the master components. If you want your master node to act both as master (api,scheduler,controller) and node (e.g. accept workloads, create pods ...),
the server address has to be present on both groups 'kube-master' and 'kube-node'.
* Almost all kubernetes components are running into pods except *kubelet*. These pods are managed by kubelet which ensure they're always running
* One etcd cluster member per node will be configured. For safety reasons, you should have at least two master nodes.
### Network Overlay ### Network Overlay
You can choose between 2 network plugins. Only one must be chosen. You can choose between 2 network plugins. Only one must be chosen.