Kimmo Lehto

The handling of ssh configuration and known hosts files is indeed flawed in many ways.

First and the most obvious is the change of `externalAddress` when a new token needs to be generated as the address is inside the token. So, if that is detected,...

It could make sense to wait for workers to get the new kube-proxy after control plane is upgraded before proceeding to upgrade them.

As you mentioned in https://github.com/k0sproject/k0s/issues/5668 - it would be more useful if k0s had a schema and then the k0sctl's schema for `spec.k0s.config` should somehow adapt to `spec.k0s.version` (though, it...

With [`files`](https://github.com/k0sproject/k0sctl/blob/main/README.md#spechostsfiles-sequence-optional) / [`hooks`](https://github.com/k0sproject/k0sctl/blob/main/README.md#spechostshooks-mapping-optional) overwriting `server.crt` and `server.key` in `/var/lib/k0s/pki`, you _could_ be able to pull off getting the same cert on all nodes but there are security concerns and...

k0sctl also has the ID_LIKE override that you could use if chimera was based on some supported distro. ```yaml apiVersion: ... spec: hosts: - role: controller os: debian ``` but...

"k0s status" for windows is now in main, maybe you can use it here.