k3s/contrib/ansible
Tim Hockin 3005471100 Add new apiserver flags for clusterIP (nee portal)
Leave old flags but marked as deprecated
2015-05-28 16:10:44 -07:00
..
group_vars Just put all vars in all.yml 2015-04-03 13:01:13 -04:00
roles Add new apiserver flags for clusterIP (nee portal) 2015-05-28 16:10:44 -07:00
.gitignore example ansible setup repo 2015-04-03 12:01:36 -04:00
README.md Add ga-beacon analytics to gendocs scripts 2015-05-15 18:56:38 -07:00
cluster.yml example ansible setup repo 2015-04-03 12:01:36 -04:00
etcd.yml example ansible setup repo 2015-04-03 12:01:36 -04:00
inventory example ansible setup repo 2015-04-03 12:01:36 -04:00
kubernetes-services.yml example ansible setup repo 2015-04-03 12:01:36 -04:00

README.md

Kubernetes Ansible

This playbook helps you to set up a Kubernetes cluster on machines where you can't or don't want to use the salt scripts and cluster up/down tools. They can be real hardware, VMs, things in a public cloud, etc.

Usage

  • Record the IP address of which machine you want to be your master
  • Record the IP address of the machine you want to be your etcd server (often same as master)
  • Record the IP addresses of the machines you want to be your minions. (master can be a minion)

Stick the system information into the 'inventory' file.

Configure your cluster

You will want to look though all of the options in group_vars/all.yml and set the variables to reflect your needs. The options should be described there in full detail.

Set up the actual kubernetes cluster

Now run the setup:

$ ansible-playbook -i inventory cluster.yml

In generel this will work on very recent Fedora, rawhide or F21. Future work to support RHEL7, CentOS, and possible other distros should be forthcoming.

You can just set up certain parts instead of doing it all

Only the kubernetes daemons:

$ ansible-playbook -i inventory kubernetes-services.yml

Only etcd:

$ ansible-playbook -i inventory etcd.yml

Only flannel:

$ ansible-playbook -i inventory flannel.yml

Analytics