k0sctl
k0sctl copied to clipboard
Extra \x20 in the service file
ExecStart=/usr/local/bin/k0s controller --config=/etc/k0s/k0s.yaml --data-dir=/var/lib/k0s --enable-k0s-cloud-provider=true --enable-worker=true --k0s-cloud-provider-update-frequency=30s --kube-controller-manager-extra-args=--v=0\x20--logging-format=json --kubelet-extra-args=--v=0\x20--node-ip=100.64.0.136\x20--hostname-override=xxxx--no-taints=true --token-file=/etc/k0s/k0stoken
- role: controller+worker
noTaints: true
privateAddress: 100.64.0.136
hostname: xxxx
ssh:
address: xxxx
user: root
installFlags:
- --kubelet-extra-args="--v=0"
- --kube-controller-manager-extra-args="--v=0 --logging-format=json"
- --enable-k0s-cloud-provider=true
- --k0s-cloud-provider-update-frequency 30s
Not sure why
Interesting. It's also possible this happens in k0s install, do you happen to have the debug log line where k0sctl runs sudo k0s install controller .......?
Interesting. It's also possible this happens in
k0s install, do you happen to have the debug log line where k0sctl runssudo k0s install controller .......?
time="19 Feb 24 12:31 CST" level=debug msg="[ssh] xxxx:22: executing `/usr/local/bin/k0s install controller --kubelet-extra-args=\"--v=0 --node-ip=100.64.0.136 --hostname-override=xxxx\" --kube-controller-manager-extra-args=\"--v=0 --logging-format=json\" --enable-k0s-cloud-provider=true --k0s-cloud-provider-update-frequency 30s --data-dir=/var/lib/k0s --enable-worker --no-taints --token-file \"/etc/k0s/k0stoken\" --config \"/etc/k0s/k0s.yaml\"`"
Looks like it left k0sctl correctly, maybe the problem is in k0s, but that should have been noticed earlier. Need to investigate further.