@agreeable-oil-87482 i hope you don't mind me asking but i was watching your video on provisioning rancher on vsphere infrastructure. i am trying to emulate the way you assigned ip addresses with the network protocol profile but i wasn't quite sure if i got it right. i understand how you got the ip address metra data from the vaspp to the vm through cloud init but how does the ip get to the vapp /vm allocation? many thanks for your help

Hey, I don't mind at all. I wrote a blog post that covers the end to end process https://www.virtualthoughts.co.uk/2020/03/29/rancher-vsphere-network-protocol-profiles-and-static-ip-addresses-for-k8s-nodes/

Thank you @agreeable-oil-87482. is the portgroup needed or can we choose network?

Not sure I follow. A portgroup is a network

I should say vSwitch or distributed vSwitch.

I think it's for vds only

@agreeable-oil-87482 thank you very much for your help. I had to reread a few times but I finally got the network address pool going. It works with a normal vswitch. The missing peice is that your information in the rancher vapp is actually what is supplied with the dynamic settings when set in the vapps properties. I have to test out the parsing part and because we use rhel then it is a different ip address setting but that extrapolation of the networking info is very nifty. Thank you very much!

You're most welcome. Yeah the script that's sent to cloud-init will need a slight tweak depending on the OS/Network manager being used, interface names etc.