Tom Wieczorek

When #4660 gets released, you should be able to use the following to circumvent the problem: ```yaml apiVersion: k0s.k0sproject.io/v1beta1 kind: ClusterConfig metadata: name: k0s spec: # [...] extensions: helm: repositories:...

Nice. There's also spf13/cobra#2018 which enables better plugin support. I think I remember that we had some workarounds for that that we might be able to drop now, too.

I'm pondering if we can use that new functionality verbatim. IIUC the new upstream solution calls all the PersistentPreRun hooks, starting with the root until it reaches the actual command....

This is a bit repetitive, but it still remains valid: The get.k0s.sh script is just a glorious `curl` wrapper for a single binary download. Everything else (installation / reset) is...

> BTW will the systemd unit removed as well? `k0s reset` will remove that as well. > And very often I get a message that k0s reset can not talk...

Do you have a specific use case in mind where this could be helpful, or is this a general good-to-know type of information?

> I wonder if it actually makes sense to let k0s sysinfo check filesystem type of `/var/lib/k0s` since datadir is configurable. Maybe it would be better to add something to...

Additionally, there are quite some `Fatal` calls on logrus loggers, which will call `os.Exit` under the hood.

You can let k0s apply those if you put the resource files into a folder below `/var/lib/k0s/manifests`. When deploying k0s via k0sctl, you could reference the files in k0sctl.yaml to...

> We'd be happy to review PRs if you'd like to make those changes. I have an experimental branch for this, indeed. > I'm also curious to know if you...