hosts: Add Kubernetes machines

There is no specific playbook or role for Kubernetes.  All OS
configuration is done at install time via kickstart scripts, and
deploying Kubernetes itself is done (manually) using `kubeadm init` and
`kubeadm join`.

group_vars/k8s-controller.yml

@@ -0,0 +1 @@
+collectd_processes: '{{ collectd_processes_kubelet + collectd_processes_controller}}'

group_vars/k8s-node.yml

@@ -0,0 +1 @@
+collectd_processes: '{{ collectd_processes_kubelet }}'

group_vars/kubelet.yml

@@ -0,0 +1,10 @@
+samba_interfaces:
+- '{{ ansible_default_ipv4.interface }}'
+host_uses_firewalld: false
+collectd_processes_kubelet:
+- name: crio
+- name: kubelet
+collectd_processes_controller:
+- name: etcd
+- name: kube-apiserver
+- name: kube-controller

hosts

@@ -66,6 +66,18 @@ hass2.pyrocufflink.blue
 [jenkins-slave]
 build0-amd64.pyrocufflink.blue
 
+[k8s-controller]
+k8s-ctrl0.pyrocufflink.blue
+
+[k8s-node]
+k8s-amd64-n0.pyrocufflink.blue
+k8s-amd64-n1.pyrocufflink.blue
+k8s-amd64-n2.pyrocufflink.blue
+
+[kubelet:children]
+k8s-controller
+k8s-node
+
 [motioneye]
 
 [named-server:children]
@@ -104,6 +116,10 @@ file0.pyrocufflink.blue
 git0.pyrocufflink.blue
 hass2.pyrocufflink.blue
 jenkins0.pyrocufflink.blue
+k8s-amd64-n0.pyrocufflink.blue
+k8s-amd64-n1.pyrocufflink.blue
+k8s-amd64-n2.pyrocufflink.blue
+k8s-ctrl0.pyrocufflink.blue
 logs0.pyrocufflink.blue
 matrix0.pyrocufflink.blue
 nvr1.pyrocufflink.blue