Torsten Curdt

I guess it would be good to create PR for this - but I am a little lost on what still needs to be done.

Would also love to see this added.

Urgh - still no word?

I think I have a related question. Vagrant also provides a custom ssh config `vagrant ssh-config` to ssh into the VMs. ``` Host node1 HostName 127.0.0.1 User vagrant Port 2222...

> I think the word "just" doesn't really work here, that's rather a lot of change for this use-case. That was just the birds eye view with a sprinkle of...

Not quite as easy apparently: ``` k3sup install --ip=192.168.100.101 --user=vagrant \ --k3s-extra-args "--node-external-ip=192.168.100.101" % kubectl get node -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME node1...

I made some progress: ``` k3sup install --ip=192.168.100.101 --user=vagrant --ssh-key=/Users/foo/servers/.vagrant/machines/node1/virtualbox/private_key \ --k3s-extra-args "--flannel-iface=eth1" ``` This looks OK now. But joining is a problem: ``` k3sup join --ip=192.168.100.102 --user=vagrant --ssh-key=/Users/foo/servers/.vagrant/machines/node2/virtualbox/private_key \...

2.6.9 still fails and 2.8.0 works (both with `application/json`) for me. Something must have changed.

Seems like there were quite some changes in `hook.go` that could have an impact.

2.7.0 also fails.