Kimmo Lehto
Kimmo Lehto
There's other stuff too that would benefit from some kind of adapter layer for different k0s versions.
Yes worker profiles aren't understood by k0sctl so you need to use the `--profile` installFlag. Maybe this could be implemented so it would become a configuration setting.
Sounds good to me.
Too bad there's no coreos image for footloose so we could add it to the test matrix. I assume you've tried this build with an actual coreos installation? :)
I assume it will need some directory tweaks to avoid writing to `/usr`?
Looks fine to me, I assume you've used it succesfully?
> I noticed that k0sctl wants to upgrade even if the target host is already running the correct version. Yes, this always happens when `k0sBinaryPath` or `files:` is used because...
> A second run of k0sctl also fails because it tries to join new controllers by requesting a token from the wrong node (the newly created one which hasn't been...
> `tee: /usr/local/bin/k0s: Text file busy` The only possible explanation for this is that k0s is still running when trying to replace the binary.
Hmmm, this is a forced upgrade because of the presence of `files`. The "upload binaries" phase should be skipped because k0s is going to be upgraded. There's some error in...