Kimmo Lehto
Kimmo Lehto
Is this cgroup thing something k0sctl should detect and maybe configure it or fail?
Currently k0sctl does not care if there are nodes in the cluster that do not exist in the config. Could you have a k0sctl config that has the controllers and...
Currently k0sctl doesn't do anything about the dynamic config (#270) but it will soon. Changing the config in k0sctl.yaml won't make a difference once the cluster is in dynamic mode....
My guess is that it is ignored, @jnummelin will know better.
I think it needs to know which labels were set by k0sctl so it can remove the ones that no longer exist in k0sctl.yaml Maybe some `k0sctl.k0sproject.io/node-labels` annotation of the...
Maybe a configMap
That's strange. The only thing k0sctl should be doing when using `single` role is to add `--single` to k0s install flags.
`k0s config create` creates a config with `storage.type: etcd`, but k0sctl should only do that when there's no `spec.k0s.config` at all.
This may actually be a problem in k0s, if you provide a partial config to a cluster with `--single`, it will pick up etcd. https://github.com/k0sproject/k0s/issues/1707 related.
For this and #73 we need some signing keys, @mviitane maybe you can get hold of those. For launchpad we're still waiting after a year or so.