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.

187 lines
9.1 KiB

6 years ago
6 years ago
6 years ago
contiv network support (#1914) * Add Contiv support Contiv is a network plugin for Kubernetes and Docker. It supports vlan/vxlan/BGP/Cisco ACI technologies. It support firewall policies, multiple networks and bridging pods onto physical networks. * Update contiv version to 1.1.4 Update contiv version to 1.1.4 and added SVC_SUBNET in contiv-config. * Load openvswitch module to workaround on CentOS7.4 * Set contiv cni version to 0.1.0 Correct contiv CNI version to 0.1.0. * Use kube_apiserver_endpoint for K8S_API_SERVER Use kube_apiserver_endpoint as K8S_API_SERVER to make contiv talks to a available endpoint no matter if there's a loadbalancer or not. * Make contiv use its own etcd Before this commit, contiv is using a etcd proxy mode to k8s etcd, this work fine when the etcd hosts are co-located with contiv etcd proxy, however the k8s peering certs are only in etcd group, as a result the etcd-proxy is not able to peering with the k8s etcd on etcd group, plus the netplugin is always trying to find the etcd endpoint on localhost, this will cause problem for all netplugins not runnign on etcd group nodes. This commit make contiv uses its own etcd, separate from k8s one. on kube-master nodes (where net-master runs), it will run as leader mode and on all rest nodes it will run as proxy mode. * Use cp instead of rsync to copy cni binaries Since rsync has been removed from hyperkube, this commit changes it to use cp instead. * Make contiv-etcd able to run on master nodes * Add rbac_enabled flag for contiv pods * Add contiv into CNI network plugin lists * migrate contiv test to tests/files Signed-off-by: Cristian Staretu <cristian.staretu@gmail.com> * Add required rules for contiv netplugin * Better handling json return of fwdMode * Make contiv etcd port configurable * Use default var instead of templating * roles/download/defaults/main.yml: use contiv 1.1.7 Signed-off-by: Cristian Staretu <cristian.staretu@gmail.com>
7 years ago
  1. ![Kubernetes Logo](https://raw.githubusercontent.com/kubernetes-incubator/kubespray/master/docs/img/kubernetes-logo.png)
  2. Deploy a Production Ready Kubernetes Cluster
  3. ============================================
  4. If you have questions, join us on the [kubernetes slack](https://kubernetes.slack.com), channel **\#kubespray**.
  5. You can get your invite [here](http://slack.k8s.io/)
  6. - Can be deployed on **AWS, GCE, Azure, OpenStack, vSphere, Oracle Cloud Infrastructure (Experimental), or Baremetal**
  7. - **Highly available** cluster
  8. - **Composable** (Choice of the network plugin for instance)
  9. - Supports most popular **Linux distributions**
  10. - **Continuous integration tests**
  11. Quick Start
  12. -----------
  13. To deploy the cluster you can use :
  14. ### Ansible
  15. # Install dependencies from ``requirements.txt``
  16. sudo pip install -r requirements.txt
  17. # Copy ``inventory/sample`` as ``inventory/mycluster``
  18. cp -rfp inventory/sample/* inventory/mycluster
  19. # Update Ansible inventory file with inventory builder
  20. declare -a IPS=(10.10.1.3 10.10.1.4 10.10.1.5)
  21. CONFIG_FILE=inventory/mycluster/hosts.ini python3 contrib/inventory_builder/inventory.py ${IPS[@]}
  22. # Review and change parameters under ``inventory/mycluster/group_vars``
  23. cat inventory/mycluster/group_vars/all.yml
  24. cat inventory/mycluster/group_vars/k8s-cluster.yml
  25. # Deploy Kubespray with Ansible Playbook
  26. ansible-playbook -i inventory/mycluster/hosts.ini cluster.yml
  27. Note: When Ansible is already installed via system packages on the control machine, other python packages installed via `sudo pip install -r requirements.txt` will go to a different directory tree (e.g. `/usr/local/lib/python2.7/dist-packages` on Ubuntu) from Ansible's (e.g. `/usr/lib/python2.7/dist-packages/ansible` still on Ubuntu).
  28. As a consequence, `ansible-playbook` command will fail with:
  29. ```
  30. ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.
  31. ```
  32. probably pointing on a task depending on a module present in requirements.txt (i.e. "unseal vault").
  33. One way of solving this would be to uninstall the Ansible package and then, to install it via pip but it is not always possible.
  34. A workaround consists of setting `ANSIBLE_LIBRARY` and `ANSIBLE_MODULE_UTILS` environment variables respectively to the `ansible/modules` and `ansible/module_utils` subdirectories of pip packages installation location, which can be found in the Location field of the output of `pip show [package]` before executing `ansible-playbook`.
  35. ### Vagrant
  36. For Vagrant we need to install python dependencies for provisioning tasks.
  37. Check if Python and pip are installed:
  38. python -V && pip -V
  39. If this returns the version of the software, you're good to go. If not, download and install Python from here <https://www.python.org/downloads/source/>
  40. Install the necessary requirements
  41. sudo pip install -r requirements.txt
  42. vagrant up
  43. Documents
  44. ---------
  45. - [Requirements](#requirements)
  46. - [Kubespray vs ...](docs/comparisons.md)
  47. - [Getting started](docs/getting-started.md)
  48. - [Ansible inventory and tags](docs/ansible.md)
  49. - [Integration with existing ansible repo](docs/integration.md)
  50. - [Deployment data variables](docs/vars.md)
  51. - [DNS stack](docs/dns-stack.md)
  52. - [HA mode](docs/ha-mode.md)
  53. - [Network plugins](#network-plugins)
  54. - [Vagrant install](docs/vagrant.md)
  55. - [CoreOS bootstrap](docs/coreos.md)
  56. - [Debian Jessie setup](docs/debian.md)
  57. - [openSUSE setup](docs/opensuse.md)
  58. - [Downloaded artifacts](docs/downloads.md)
  59. - [Cloud providers](docs/cloud.md)
  60. - [OpenStack](docs/openstack.md)
  61. - [AWS](docs/aws.md)
  62. - [Azure](docs/azure.md)
  63. - [vSphere](docs/vsphere.md)
  64. - [Large deployments](docs/large-deployments.md)
  65. - [Upgrades basics](docs/upgrades.md)
  66. - [Roadmap](docs/roadmap.md)
  67. Supported Linux Distributions
  68. -----------------------------
  69. - **Container Linux by CoreOS**
  70. - **Debian** Jessie, Stretch, Wheezy
  71. - **Ubuntu** 16.04, 18.04
  72. - **CentOS/RHEL** 7
  73. - **Fedora/CentOS** Atomic
  74. - **openSUSE** Leap 42.3/Tumbleweed
  75. Note: Upstart/SysV init based OS types are not supported.
  76. Supported Components
  77. --------------------
  78. - Core
  79. - [kubernetes](https://github.com/kubernetes/kubernetes) v1.11.3
  80. - [etcd](https://github.com/coreos/etcd) v3.2.18
  81. - [docker](https://www.docker.com/) v17.03 (see note)
  82. - [rkt](https://github.com/rkt/rkt) v1.21.0 (see Note 2)
  83. - Network Plugin
  84. - [calico](https://github.com/projectcalico/calico) v3.1.3
  85. - [canal](https://github.com/projectcalico/canal) (given calico/flannel versions)
  86. - [cilium](https://github.com/cilium/cilium) v1.2.0
  87. - [contiv](https://github.com/contiv/install) v1.1.7
  88. - [flanneld](https://github.com/coreos/flannel) v0.10.0
  89. - [weave](https://github.com/weaveworks/weave) v2.4.1
  90. - Application
  91. - [cephfs-provisioner](https://github.com/kubernetes-incubator/external-storage) v2.1.0-k8s1.11
  92. - [cert-manager](https://github.com/jetstack/cert-manager) v0.5.0
  93. - [coredns](https://github.com/coredns/coredns) v1.2.2
  94. - [ingress-nginx](https://github.com/kubernetes/ingress-nginx) v0.19.0
  95. Note: kubernetes doesn't support newer docker versions ("Version 17.03 is recommended... Versions 17.06+ might work, but have not yet been tested and verified by the Kubernetes node team" cf. [Bootstrapping Clusters with kubeadm](https://kubernetes.io/docs/setup/independent/install-kubeadm/#installing-docker)). Among other things kubelet currently breaks on docker's non-standard version numbering (it no longer uses semantic versioning). To ensure auto-updates don't break your cluster look into e.g. yum versionlock plugin or apt pin).
  96. Note 2: rkt support as docker alternative is limited to control plane (etcd and
  97. kubelet). Docker is still used for Kubernetes cluster workloads and network
  98. plugins' related OS services. Also note, only one of the supported network
  99. plugins can be deployed for a given single cluster.
  100. Requirements
  101. ------------
  102. - **Ansible v2.4 (or newer) and python-netaddr is installed on the machine
  103. that will run Ansible commands**
  104. - **Jinja 2.9 (or newer) is required to run the Ansible Playbooks**
  105. - The target servers must have **access to the Internet** in order to pull docker images.
  106. - The target servers are configured to allow **IPv4 forwarding**.
  107. - **Your ssh key must be copied** to all the servers part of your inventory.
  108. - The **firewalls are not managed**, you'll need to implement your own rules the way you used to.
  109. in order to avoid any issue during deployment you should disable your firewall.
  110. - If kubespray is ran from non-root user account, correct privilege escalation method
  111. should be configured in the target servers. Then the `ansible_become` flag
  112. or command parameters `--become or -b` should be specified.
  113. Network Plugins
  114. ---------------
  115. You can choose between 6 network plugins. (default: `calico`, except Vagrant uses `flannel`)
  116. - [flannel](docs/flannel.md): gre/vxlan (layer 2) networking.
  117. - [calico](docs/calico.md): bgp (layer 3) networking.
  118. - [canal](https://github.com/projectcalico/canal): a composition of calico and flannel plugins.
  119. - [cilium](http://docs.cilium.io/en/latest/): layer 3/4 networking (as well as layer 7 to protect and secure application protocols), supports dynamic insertion of BPF bytecode into the Linux kernel to implement security services, networking and visibility logic.
  120. - [contiv](docs/contiv.md): supports vlan, vxlan, bgp and Cisco SDN networking. This plugin is able to
  121. apply firewall policies, segregate containers in multiple network and bridging pods onto physical networks.
  122. - [weave](docs/weave.md): Weave is a lightweight container overlay network that doesn't require an external K/V database cluster.
  123. (Please refer to `weave` [troubleshooting documentation](http://docs.weave.works/weave/latest_release/troubleshooting.html)).
  124. The choice is defined with the variable `kube_network_plugin`. There is also an
  125. option to leverage built-in cloud provider networking instead.
  126. See also [Network checker](docs/netcheck.md).
  127. Community docs and resources
  128. ----------------------------
  129. - [kubernetes.io/docs/getting-started-guides/kubespray/](https://kubernetes.io/docs/getting-started-guides/kubespray/)
  130. - [kubespray, monitoring and logging](https://github.com/gregbkr/kubernetes-kargo-logging-monitoring) by @gregbkr
  131. - [Deploy Kubernetes w/ Ansible & Terraform](https://rsmitty.github.io/Terraform-Ansible-Kubernetes/) by @rsmitty
  132. - [Deploy a Kubernetes Cluster with Kubespray (video)](https://www.youtube.com/watch?v=N9q51JgbWu8)
  133. Tools and projects on top of Kubespray
  134. --------------------------------------
  135. - [Digital Rebar Provision](https://github.com/digitalrebar/provision/blob/master/doc/integrations/ansible.rst)
  136. - [Fuel-ccp-installer](https://github.com/openstack/fuel-ccp-installer)
  137. - [Terraform Contrib](https://github.com/kubernetes-incubator/kubespray/tree/master/contrib/terraform)
  138. CI Tests
  139. --------
  140. [![Build graphs](https://gitlab.com/kubespray-ci/kubernetes-incubator__kubespray/badges/master/build.svg)](https://gitlab.com/kubespray-ci/kubernetes-incubator__kubespray/pipelines)
  141. CI/end-to-end tests sponsored by Google (GCE)
  142. See the [test matrix](docs/test_cases.md) for details.