This message was deleted.
# general
a
This message was deleted.
c
Are you asking about rke or rke2?
The embedded helm controller doesn't render it to a template, it installs it directly to the cluster. If you're getting that error, then at least one of your server nodes is still running 1.20
Can you confirm that all of your nodes have been upgraded?
f
This is truly on an install of RKE2 v1.24.11 freshly terraformed a couple of times a day as I develop. It is a cluster of (3) control plane nodes and (3) worker nodes. The deployment is being performed by Fleet 102.0.0+up0.6.0. The message about "chart requires kubeVersion" is appearing in the event log of the bundle for Argo CD as well as for versions of cert-manager > v1.10.0 when they started added kubeVersion restrictions in their Chart.yaml. I presumed (perhaps incorrectly) Fleet leveraged the internal helm controller and HelmChart kind to do its work. Does Fleet NOT use the embedded helm controller but an external one?
I did notice that the Fleet source for 0.6.0 has hardcoded the tag for its kubectl container image to v1.21 so I was looking for similar for a helm executable that Fleet might use.
c
The embedded HelmChart controller in rke2 is unrelated to fleet. It is it's own thing that works very differently. Can you clarify which one you're using?
f
I'm definitely using the Fleet one then, since each chart I'm installing is being done as a bundle and the error message is attached to the bundle's event: field. So the question is whether Fleet is calling out to a helm executable or whether Fleet has incorporated some form of library that lets it do helm installs. And of those two, which kubeVersion is the Helm implementation in Fleet equivalent to, as I'm seeing a rise in the use of kubeVersion: field in Helm charts where it was rare a year ago.