Kimmo Lehto
Kimmo Lehto
perhaps needs `Install-WindowsFeature -Name Containers -IncludeAllSubFeature -Restart` (or something that validates Containers is installed)
Some features (status, reset) are still missing from k0s on windows so those need to be implemented first.
(also `k0sctl status`?)
There's this old issue https://github.com/k0sproject/k0sctl/issues/175 about adding labeling support. Until that, maybe you could use after-hooks to run `k0s kubectl ....`.
Yes I've been thinking about this too. Especially with #923. And it could lead to an automated incremental upgrade using the recommended upgrade path (so something like 1.31.1 => 1.31.8...
I think mDns does not work with static go binaries out of the box. It could be possible to import something like https://github.com/hashicorp/mdns and use it to resolve and replace...
I made an experimental PR to add support but I'm not convinced it's the right approach. You can try it if you want to.
This was closed with wrong fix, time skew and version skew are a different thing :)
So, I assume you see this for the workers: ```go log.Infof("%s: checking if worker %s has joined", p.leader, h.Metadata.Hostname) ``` After looking for `admin.conf`, k0sctl should fall back to using...