C12s/c12s-kubespray
3
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
Deploy a Production Ready Kubernetes Cluster on bare metal or raw VMs - This is a clone of https://github.com/kubernetes-sigs/kubespray.git with a kitten twist.
2 commits 17 branches 66 tags 141 MiB
Jinja 78.9%
HCL 10%
Python 5.7%
Shell 4.5%
Groovy 0.2%
Other 0.6%
Go to file
Smaine Kahlouch 00c562828f Initial commit
2015-10-03 22:19:50 +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 Initial commit 2015-10-03 22:19:50 +02:00
cluster.yml Initial commit 2015-10-03 22:19:50 +02:00
README.md Initial commit 2015-10-03 22:19:50 +02:00

README.md

This playbook deploys a whole kubernetes cluster, configures network overlay and some addons.

Download necessary binaries

Note: a variable 'local_release_dir' defines where the binaries will be downloaded. Ensure you've enough disk space

Kubernetes

Kubernetes services are configured with the nodePort type. eg: each node opoens the same tcp port and forwards the traffic to the target pod wherever it is located.

master :

  • apiserver : Currently the apiserver listen on both secure and unsecure ports todo, secure everything. Calico especially
  • scheduler :
  • controller :
  • proxy node :
  • kubelet : kubelet is configured to call calico whenever a pod is created/destroyed
  • proxy configures all the forwarding rules

Overlay network

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

Loadbalancer

The machine where ansible is ran must be allowed to access to the master ip on port 8080 (kubernetes api). Indeed it gathered the services definition in order to know which NodePort is configured.