Hello, I'm experiencing an issue with a lot of the features Elemental has documented in the 1.7 version. First: https://elemental.docs.rancher.com/label-templates-network

rancher-17978:~ # elemental-register dumpdata | grep -i IPv4Address
rancher-17978:~ #

I see plenty of the network keys, but no IPv4Address records. Second: https://elemental.docs.rancher.com/rancher-ip/ I've of course tried the method which uses labels from the network template, but, because there is no such thing as an "IPv4Address" key, that label doesn't work. Further, if I set these labels manually, they're ignored completely on Rancher cluster creation, and RKE2 seems to prefer to use the exact wrong IP every time. So there is no effective way to select the IP addresses. Third: I use IPAM for my addressing, so I figured I could just dump a yaml file into /etc/rancher/rke2/config.yaml.d/ with the appropriate settings via cloud-init, but it seems the {internal} and {external} string replacements are only available in the network key of cloud-init. This is likely not a bug, but would be a great feature enhancement. Ultimately, I'm asking "How the heck do I set an IP address for my RKE2 since all methods in documentation don't work as advertised"? I want my organization to adopt RKE2/Rancher/Elemental across all of our datacenters, but this bridge is a bit hard to get by. I'm considering writing a webhook to populate the labels to the node automatically based on the IPAM claims to mutate the

MachineInventory

resource as they're created from the

spec.network.ipAddresses.*

keys, or even match up the claims, but without the label working from issue 2, it's a pointless exercise.