cri-o
/
cri-o-ansible
mirror of https://github.com/cri-o/cri-o-ansible.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Playbooks to install CRI-O from source
52 Commits 1 Branch 0 Tags 86 KiB
Go to file
Antonio Murdaca 71498e8785 Merge pull request #15 from aweiteka/runc_link 
make playbook more idempotent when linking runc
 		2017-07-26 14:52:44 +02:00
group_vars add "runtime" variable to select between runc and cc-oci-runtime 2017-07-06 08:49:32 -05:00
install add "runtime" variable to select between runc and cc-oci-runtime 2017-07-06 08:49:32 -05:00
.gitignore Add *.retry to .gitignore 2017-06-21 10:37:48 -05:00
README.md Install kubernetes 2017-06-21 10:22:07 -05:00
cri-o.yml make playbook more idempotent when linking runc 2017-07-25 14:26:46 -04:00

README.md

This playbook provisions a CentOS 7.3/Ubuntu 16.04/RHEL/Fedora 25+ machine with everything you need in order to use kubeadm and CRI-O (no docker anymore). Simply run:

Create an ansible hosts file (adjust anything needed like ansible_python_interpreter):

$ cat hosts
192.168.1.122 ansible_python_interpreter='python3'
192.168.1.123

make sure the machine is reachable via SSH w/o password input before running the playbook

ssh-copy-id <user>@<ip or hostname>

Then simply run:

$ ansible-playbook -i hosts cri-o.yml -u <user>

This playbook installs kubernetes software so you can follow the kubeadm docs to setup a Kubernetes cluster. I've tested the whole flow with a custom Flannel pod network, the official one seems broken.

What is cri-o-ansible not doing?

  • cri-o-ansible is not going to install any CNI network configuration. It just installs CNI plugins. Network configuration is left to Kubernetes and Openshift (or you following this)