This message was deleted.
# harvester
a
This message was deleted.
👀 1
r
Would you provide more details regarding your question? I just span up a Rancher v2.7.5 and Harvester v1.1.2, and I could deploy an RKE2 v1.24.15 guest cluster with them without problems 🤔
s
Sorry, didn’t see this notification. Sure, what details would be helpful? I’ve left all other settings as default on the page. If I try to select any rke2 version higher than 1.23.17, the
Harvester
option in the Cloud Provider dropdown is grayed out and cannot be selected and I see the notice in the screenshot above.
Ah, I just realized if I checkmark
Show deprecated Kubernetes patch versions
, I can select 1.24.14 and it will allow that. It will also allow 1.25, 1.26 deprecated versions too. So, that leads to the question, why do I need to choose deprecated versions for a new cluster?
r
Yes, we’ve realized this problem, as it confuses users and makes it impossible to use the Harvester cloud provider with the newest patch version of RKE2. The workaround is to choose an older version, as you mentioned above. For RKE2 v1.24, you have to choose specifically v1.24.14+rke2r1 to be able to use the Harvester cloud provider. The reason is the Harvester cloud provider is coupled with RKE2's releases. The newest RKE2 releases, e.g., v1.24.15+rke2r1, are already bundled with the newest Harvester cloud provider (0.2.2), but it requires the underlying Harvester cluster to be in v1.2.0, which is apparently a conflict. That is, to use the Harvester cloud provider on Harvester v1.1.2 clusters, we need to step back a little with RKE2 v1.24.14+rke2r1. This will be addressed in a future release. Thanks for reporting! cc @orange-policeman-97710