This message was deleted.
# vsphere
a
This message was deleted.
w
The documentation for the latest release refers to creating a node template and creating the cluster using that template so a bit confused. https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/launch-kubernetes-with[…]ider/vsphere/provision-kubernetes-clusters-in-vsphere
s
6.7 is EOM, but you seem to be confusing rke1 and rke2/k3s. RKE1 requires a ‘node template’ where you pre-define stuff for your cluster. This can be re-used between pools in rancher, or you can create new templates for your use case. rke2 doesn’t require a node template, but does require you fill out the node information for each pool. To see this, go back to the management -> create cluster view and toggle the ‘rke2/k3s’ icon before selecting vsphere from the page.
w
Oh, I'm definitely confused. Thanks for pointing out the RKE2/k3a toggle - knew I'd seen it somewhere on this system. I've deployed a couple of RKE2 clusters onto vSphere already but that's meant me entering a few options each time for the usual stuff like data center, data store etc but I've needed to add cloud config and vApp properties as well each time.
I was hoping I could put all this into a reusable template as the only things I'm likely to change in subsequent deployments are the cluster name and maybe some CPU/RAM values which leads me to believe I should be looking at RKE2 Cluster templates instead? I'll watch that Masterclass and see if I can wrap my head around it. Thanks.
👍 1