Allow specifying labels for the `helm.k0sproject.io/v1beta1` objects about k0s HOT 3 OPEN

Though I imagine you'd recommend just creating chart objects in the cluster ourselves in that scenario? It would simplify some other logic of ours I suppose

Yes, this is more versatile. The charts specified in the k0s config aren't any special compared to user-managed chart resources. And if you're using dynamic config already, then it's potentially not too hard to reconcile additional chart resources in addition to the k0s cluster config resource, I suppose.

from k0s.

You can already do arbitrary things with Chart resources if you manage them as plain manifests by placing yaml files into <data-dir>/manifests instead of putting them into the k0s config directly.

from k0s.

That would work great if we weren't using Dynamic Configuration! Though I imagine you'd recommend just creating chart objects in the cluster ourselves in that scenario? It would simplify some other logic of ours I suppose

from k0s.