This message was deleted.
# rke2
a
This message was deleted.
c
I think most people just have some sort of real IPAM, whether that’s a DHCP server that supports stable reservations, or something else. Managing self-assigning your own static IPs isn’t something I see many folks struggling with.
a
Fair enough. Organizationally we're looking to modernize IPAM and change how we do DHCP on prem so I was just looking to see if this is "good enough" to hold on us over until we have something more mature in place.
I see it as a temporary issue, but also for specific env (on-prem)
k
Not sure on your infrastructure setup, but looks like you are using vSphere as the cloud provider. If so you can take a look at using vSphere Network Protocol Profiles in combination with vApp properties and cloud-init to configure a static IP to a VM using a /24 for a given vSphere network. See for example this blog https://www.virtualthoughts.co.uk/2020/03/29/rancher-vsphere-network-protocol-profiles-and-static-ip-addresses-for-k8s-nodes/ and github repo: https://github.com/frank-at-suse/vsphere_rancher_cluster?tab=readme-ov-file#static-ip-addressing