Kimmo Lehto
Kimmo Lehto
This is pretty much exactly what the CI [backup-restore test](https://github.com/k0sproject/k0sctl/blob/main/smoke-test/smoke-backup-restore.sh) does. I wonder if the token somehow expired between the backup and restore 🤔
Any ideas @k0sproject/k0s-core ?
The bugs here being: 1. apply after restore will trust the result of Ready state even though it will reflect reality only after minutes possibly 2. the smoke test does...
It would be very easy to add a confirmation prompt for every single command that is being run on a remote host, but it would be quite tedious to sit...
The config stuff will change eventually anyway as dynamic config will become the default mode of operation (https://github.com/k0sproject/k0s/issues/1452) Config diff could be a nice feature.
It wouldn't be a big deal to add confirmation prompts to those phases, I'll look into it.
I think optimally this would involve context passing and pretty much touch everything.
This is from another project using rig: ```go // Reconnect disconnects and reconnects the host's connection func (h *Host) Reconnect() error { h.Disconnect() log.Infof("%s: waiting for reconnection", h) return retry.Do(...
Kubectl is already embedded in k0s nowadays, so there's no need to install it anymore. It is used by k0sctl like `k0s kubectl get nodes`. Only the smoke-tests use a...
Installed but not running perhaps?