There's no hooks into the Windows OS (it doesn't have cloud-init)

So you'd need to do your own image/sysprep to get scripts to run that would join the harvester node via the registration link

Possible, but it wouldn't just work out of box.

i know how to get a windows node attached to a generic cluster, i do it all the time, i basically get the node ready by installing updates and container services and what-not, ip the machine, name it, and then i register it as a windows worker node using the link provided in rancher cluster manager. i'm looking to do a similar thing but i dont know how to get the registration link for the windows machine.

I do that all the time because of kube-vip

just use the generic one. It'll still provision in harvester.

Or are you talking about the rancher link?

Or do you mean this one?

because the second one is a link to rancher and not rke2

But it will probably take additional work on your end and I don't think it's supported

but maybe someone at Suse knows something I don't/

You'd have to have a machine pool and go in and manualy register the windows nodes.

You could potentially script that with ansible, but it wouldn't be easy

The "link" would be the cluster token for node registration.

but it wouldn't point through rancher, that's a custom cluster thing that rancher does.

There's nothing in Harvester to bootstrap the windows box (like cloud-init) The official docs even have you image from an ISO instead of creating an imagehttps://docs.harvesterhci.io/v1.1/vm/create-windows-vm/

That being said, you could do something like use ansible to run a playbook that launches X number of VMs waits for their IPs, then has them join a cluster.

Harvester has all the API endpoints to hook into, it just doesn't have that feature set built in.

But the automatic Ansbile thing would require that you sysprep or build from WSUS or SCCM/MECM or something to get the keys in there properly.