bootloose VS k0sctl

root@ubuntu-16gb-hel1-1:~# wget -c https://github.com/k0sproject/bootloose/releases/download/v0.7.3/bootloose-linux-arm64 HTTP request sent, awaiting response... 200 OK Length: 6291456 (6.0M) [application/octet-stream] Saving to: ‘bootloose-linux-arm64’ bootloose-linux-arm64 100%[=====================================================================================================>] 6.00M 21.8MB/s in 0.3s (21.8 MB/s) - ‘bootloose-linux-arm64’ saved [6291456/6291456] root@ubuntu-16gb-hel1-1:~# chmod +x bootloose-linux-arm64 root@ubuntu-16gb-hel1-1:~# mv bootloose-linux-arm64 /usr/local/bin/bootloose root@ubuntu-16gb-hel1-1:~# bootloose bootloose - Container Machines Usage: bootloose [command] Available Commands: completion Generate the autocompletion script for the specified shell config Manage cluster configuration create Create a cluster delete Delete a cluster help Help about any command show Show all running machines or a single machine with a given hostname. ssh SSH into a machine start Start cluster machines stop Stop cluster machines version Print bootloose version Flags: -c, --config string Cluster configuration file (default "bootloose.yaml") -h, --help help for bootloose Use "bootloose [command] --help" for more information about a command.

GitHub - k0sproject/k0sctl: A bootstrapping and management tool for k0s clusters.

I thought I'd give k0s a shot and I am running in to the simplest problem. I have added my public ssh key my remote computer's authorized_key file for both root and mcamp. The private key is located at /home/mcamp/.ssh/k0s on my local computer. I am trying to deploy a whole cluster with the control plane being at 10.8.0.135. For the same of brevity I reduced my config to just make that server both a worker and a controller. Below is what I'm getting.. someone else had the EXACT same problem but they didn't share their solution.