https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
a
Hi @lively-zoo-40381, where did you find this limit, could you share a link or post a picture, will take a look, thanks.
l
Whenever I type int larger than 32, it is replaced to 32
a
Did you tried also in 
rke2
? the attached video showed operation in rke1
I guess this limit is a defined number, for running guest k8s cluster, a NODE ( namly VM in Harvester) with 32 cores are enough at that time, when more are wanted, the limit should be adjustable. In Harvester, VM can have 200+ cores.
l
RKE2 is not relevant for us. It does not matter what is the Limit in Harvester, if we are limited by the guest k8s template.
a
let me double check
What is the wanted value here ? @lively-zoo-40381
We do have a limitation,, 32 is the current barrier.
l
Wow, I didn’t see that limit of 32 cores per VM in the documentation. 1. I think this should be mentioned there 2. Is there a plan to remove this limit ? 3. When if at all will it be possible for Rancher to provision nodes directly on Harvester OS without VMs ?
Thank you @ancient-pizza-13099 for your time
a
When if at all will it be possible for Rancher to provision nodes directly on Harvester OS without VMs ?
== It is not the design target. Land k8s guest cluster in Harvester HOST NODE directly will lose many features comparing to VM, like isolation, live migration, security etc.
32-core limitation is a number defined the time, as in Rancher + Harvester scenario, the guest cluster(e.g. k8s) /workload is carried in VM, anyway we need a core number to set for the VM.
l
OK, Thanks for the information.
🤝 1
4 Views
Open in Slack
PreviousNext
Powered by