I worked around this with:
mkdir /home/harry/k8s-pi/roles/etcd/files
mkdir /home/harry/k8s-pi/roles/flannel/files
Unbelievable, I just made a working Kubernetes cluster in two hours, including unpacking the hardware :-)
Iḿ going to have so much fun with this :-)
BTW, I just used the wireless router as a NAT gateway, because my W10 laptop cannot do nat :-)
And I used a Virtualbox VM with an Ubuntu VM to run Ansible.
And it worked straight away.
During the running of the playbook I get two simple errors:
TASK [etcd : Install etcd] ***** included: /home/harry/k8s-pi/includes/install_binaries.yml for 192.168.23.200
TASK [etcd : Download Binaries] **** fatal: [192.168.23.200 -> 127.0.0.1]: FAILED! => {"changed": false, "failed": true, "msg": "Destination /home/harry/k8s-pi/roles/etcd/files not writable"}
.... and .....
TASK [flannel : Install flanneld] ** included: /home/harry/k8s-pi/includes/install_binaries.yml for 192.168.23.200
TASK [flannel : Download Binaries] ***** fatal: [192.168.23.200 -> 127.0.0.1]: FAILED! => {"changed": false, "failed": true, "msg": "Destination /home/harry/k8s-pi/roles/flannel/files not writable"}
I worked around this with: mkdir /home/harry/k8s-pi/roles/etcd/files mkdir /home/harry/k8s-pi/roles/flannel/files
Unbelievable, I just made a working Kubernetes cluster in two hours, including unpacking the hardware :-)
Iḿ going to have so much fun with this :-)
BTW, I just used the wireless router as a NAT gateway, because my W10 laptop cannot do nat :-) And I used a Virtualbox VM with an Ubuntu VM to run Ansible. And it worked straight away.