You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

210 lines
6.6 KiB

9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
  1. kubernetes-ansible
  2. ========
  3. Install and configure a kubernetes cluster including network overlay and optionnal addons.
  4. Based on [CiscoCloud](https://github.com/CiscoCloud/kubernetes-ansible) work.
  5. ### Requirements
  6. Tested on **Debian Jessie** and **Ubuntu** (14.10, 15.04, 15.10).
  7. The target servers must have access to the Internet in order to pull docker imaqes.
  8. The firewalls are not managed, you'll need to implement your own rules the way you used to.
  9. Ansible v1.9.x
  10. ### Components
  11. * [kubernetes](https://github.com/kubernetes/kubernetes/releases) v1.0.6
  12. * [etcd](https://github.com/coreos/etcd/releases) v2.2.0
  13. * [calicoctl](https://github.com/projectcalico/calico-docker/releases) v0.5.1
  14. * [flanneld](https://github.com/coreos/flannel/releases) v0.5.3
  15. * [docker](https://www.docker.com/) v1.8.2
  16. Ansible
  17. -------------------------
  18. ### Download binaries
  19. A role allows to download required binaries which will be stored in a directory defined by the variable
  20. **'local_release_dir'** (by default /tmp).
  21. Please ensure that you have enough disk space there (about **1G**).
  22. **Note**: Whenever you'll need to change the version of a software, you'll have to erase the content of this directory.
  23. ### Variables
  24. The main variables to change are located in the directory ```environments/[env_name]/group_vars/k8s-cluster.yml```.
  25. ### Playbook
  26. ```
  27. ---
  28. - hosts: downloader
  29. sudo: no
  30. roles:
  31. - { role: download, tags: download }
  32. - hosts: k8s-cluster
  33. roles:
  34. - { role: etcd, tags: etcd }
  35. - { role: docker, tags: docker }
  36. - { role: overlay_network, tags: ['calico', 'flannel', 'network'] }
  37. - { role: dnsmasq, tags: dnsmasq }
  38. - hosts: kube-master
  39. roles:
  40. - { role: kubernetes/master, tags: master }
  41. - { role: apps/k8s-kubedns, tags: ['kubedns', 'apps'] }
  42. - { role: apps/k8s-fabric8, tags: ['fabric8', 'apps'] }
  43. - hosts: kube-node
  44. roles:
  45. - { role: kubernetes/node, tags: node }
  46. ```
  47. ### Run
  48. It is possible to define variables for different environments.
  49. For instance, in order to deploy the cluster on 'dev' environment run the following command.
  50. ```
  51. ansible-playbook -i environments/dev/inventory cluster.yml -u root
  52. ```
  53. Kubernetes
  54. -------------------------
  55. ### Network Overlay
  56. You can choose between 2 network overlays. Only one must be chosen.
  57. * **flannel**: gre/vxlan (layer 2) networking. ([official docs]('https://github.com/coreos/flannel'))
  58. * **calico**: bgp (layer 3) networking. ([official docs]('http://docs.projectcalico.org/en/0.13/'))
  59. The choice is defined with the variable '**overlay_network_plugin**'
  60. ### Expose a service
  61. There are several loadbalancing solutions.
  62. The ones i found suitable for kubernetes are [Vulcand]('http://vulcand.io/') and [Haproxy]('http://www.haproxy.org/')
  63. My cluster is working with haproxy and kubernetes services are configured with the loadbalancing type '**nodePort**'.
  64. eg: each node opens the same tcp port and forwards the traffic to the target pod wherever it is located.
  65. Then Haproxy can be configured to request kubernetes's api in order to loadbalance on the proper tcp port on the nodes.
  66. Please refer to the proper kubernetes documentation on [Services]('https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/user-guide/services.md')
  67. ### Check cluster status
  68. #### Kubernetes components
  69. Master processes : kube-apiserver, kube-scheduler, kube-controller, kube-proxy
  70. Nodes processes : kubelet, kube-proxy, [calico-node|flanneld]
  71. * Check the status of the processes
  72. ```
  73. systemctl status [process_name]
  74. ```
  75. * Check the logs
  76. ```
  77. journalctl -ae -u [process_name]
  78. ```
  79. * Check the NAT rules
  80. ```
  81. iptables -nLv -t nat
  82. ```
  83. #### Available apps, installation procedure
  84. Additionnal apps can be installed with ```ansible-galaxy```.
  85. you'll need to edit the file '*requirements.yml*' in order to chose needed apps.
  86. The list of available apps are available [there](https://github.com/ansibl8s)
  87. For instance if you will probably want to install a [dns server](https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/dns) as it is **strongly recommanded**.
  88. In order to use this role you'll need the following entries in the file '*requirements.yml*'
  89. ```
  90. - src: https://github.com/ansibl8s/k8s-common.git
  91. path: roles/apps
  92. # version: v1.0
  93. - src: https://github.com/ansibl8s/k8s-kubedns.git
  94. path: roles/apps
  95. # version: v1.0
  96. ```
  97. **Note**: the role common is required by all the apps and provides the tasks and libraries needed.
  98. And empty the apps directory
  99. ```
  100. rm -rf roles/apps/*
  101. ```
  102. Then download the roles with ansible-galaxy
  103. ```
  104. ansible-galaxy install -r requirements.yml
  105. ```
  106. Finally update your playbook with the chosen role, and run it
  107. ```
  108. ...
  109. - hosts: kube-master
  110. roles:
  111. - { role: kubernetes/master, tags: master }
  112. - { role: apps/k8s-kubedns, tags: ['kubedns', 'apps'] }
  113. ...
  114. ```
  115. Please refer to the [k8s-kubdns readme](https://github.com/ansibl8s/k8s-kubedns) for additionnal info.
  116. #### Calico networking
  117. Check if the calico-node container is running
  118. ```
  119. docker ps | grep calico
  120. ```
  121. The **calicoctl** command allows to check the status of the network workloads.
  122. * Check the status of Calico nodes
  123. ```
  124. calicoctl status
  125. ```
  126. * Show the configured network subnet for containers
  127. ```
  128. calicoctl pool show
  129. ```
  130. * Show the workloads (ip addresses of containers and their located)
  131. ```
  132. calicoctl endpoint show --detail
  133. ```
  134. #### Flannel networking
  135. Congrats ! now you can walk through [kubernetes basics](http://kubernetes.io/v1.0/basicstutorials.html)
  136. Known issues
  137. -------------
  138. ### Node reboot and Calico
  139. There is a major issue with calico-kubernetes version 0.5.1 and kubernetes prior to 1.1 :
  140. After host reboot, the pods networking are not configured again, they are started without any network configuration.
  141. This issue will be fixed when kubernetes 1.1 will be released as described in this [issue](https://github.com/projectcalico/calico-kubernetes/issues/34)
  142. ### Monitoring addon
  143. Until now i didn't managed to get the monitoring addon working.
  144. ### Apiserver listen on secure port only
  145. Currently the api-server listens on both secure and insecure ports.
  146. The insecure port is mainly used for calico.
  147. Will be fixed soon.
  148. How to contribute
  149. ------------------
  150. ### Update available roles
  151. Alternatively the roles can be installed as git submodules.
  152. That way is easier if you want to do some changes and commit them.
  153. You can list available submodules with the following command:
  154. ```
  155. grep path .gitmodules | sed 's/.*= //'
  156. ```
  157. For instance if you will probably want to install a [dns server](https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/dns) as it is **strongly recommanded**.
  158. In order to use this role you'll need to follow these steps
  159. ```
  160. git submodule init roles/apps/k8s-common roles/apps/k8s-kubedns
  161. git submodule update
  162. ```