Deploy a Production Ready Kubernetes Cluster
 
 
 
 
 
Go to file
Smaine Kahlouch e74ad80fe4 Readme v2 2015-10-04 10:55:52 +02:00
environments Initial commit 2015-10-03 22:19:50 +02:00
library Initial commit 2015-10-03 22:19:50 +02:00
roles Readme v2 2015-10-04 10:55:52 +02:00
README.md Readme v2 2015-10-04 10:55:52 +02:00
cluster.yml Initial commit 2015-10-03 22:19:50 +02:00

README.md

kubernetes-ansible

Install and configure a kubernetes cluster including network overlay and optionnal addons. Based on CiscoCloud work.

Requirements

Tested on debian Jessie and Ubuntu. The target servers must have access to the Internet in order to pull docker imaqes

Ansible v1.9.x

Components

  • kubernetes v1.0.6
  • etcd v2.2.0
  • calicoctl v0.5.1
  • flanneld v0.5.3
  • docker-gc

Ansible

Download binaries

A role allows to download required binaries which will be stored in a directory defined by the variable 'local_release_dir' (by default /tmp). Please ensure that you have enough disk space there (about 1G).

Note: Whenever you'll need to change the version of a software, you'll have to erase the content of this directory.

Variables

Playbook

---
- hosts: downloader
  sudo: no
  roles:
    - { role: download, tags: download }

- hosts: k8s-cluster
  roles:
    - { role: etcd, tags: etcd }
    - { role: docker, tags: docker }
    - { role: overlay_network, tags: ['calico', 'flannel', 'network'] }
    - { role: dnsmasq, tags: dnsmasq }

- hosts: kube-master
  roles:
    - { role: kubernetes/master, tags: master }
    - { role: addons, tags: addons }

- hosts: kube-node
  roles:
    - { role: kubernetes/node, tags: node }

Run

It is possible to define variables for different environments. For instance, in order to deploy the cluster on 'dev' environment run the following command.

ansible-playbook -i environments/dev/inventory cluster.yml

Kubernetes

Check cluster status

Network Overlay

You can choose between 2 network overlays. Only one must be chosen. flannel: gre/vxlan (layer 2) networking calico: bgp (layer 3) networking.

Expose a service

There are several loadbalancing solution. The main ones i found suitable for kubernetes are Vulcand and Haproxy

My cluster is working with haproxy and kubernetes services are configured with the loadbalancing type 'nodePort'. eg: each node opens the same tcp port and forwards the traffic to the target pod wherever it is located.

Then Haproxy can be configured to request kubernetes's api in order to loadbalance on the proper tcp port on the nodes.

Please refer to the proper kubernetes documentation on Services

Known issues

Node reboot and Calico

Monitoring addon

Etcd failover

Author Information

Smana - Smaine Kahlouch (smaine.kahlouch@gmail.com)