com.vmware.guestinfo    IPv4    fixedAllocated

guestinfo.interface.0.ip.0.address  ip:atl2_dvp_devtestk8_922

guestinfo.interface.0.ip.0.netmask  ${netmask:atl2_dvp_devtestk8_922}

guestinfo.interface.0.route.0.gateway   ${gateway:atl2_dvp_devtestk8_922}

guestinfo.dns.servers   ${dns:atl2_dvp_devtestk8_922}

Fetching the vsphere credential metadata from the rancher

data "rancher2_cloud_credential" "auth" {
  name = "vsphereprgx"
}


# creating a cluster using the node pools

resource "rancher2_cluster_v2" "foo-rke2" {
  name                                     = var.cluster_name
  kubernetes_version                       = var.kubernetes_version # which kubernetes version is to be deployed
  enable_network_policy                    = var.enable_network_policy
  default_cluster_role_for_project_members = var.default_cluster_role_for_project_members
  rke_config {

    # creating the machine global config

    machine_global_config = <<EOF
      cni: ${var.cni}
      disable-kube-proxy: false
      etcd-expose-metrics: false
      kubelet-arg:
max-pods=250    
    EOF

    # creating dynamic machine pools

    dynamic "machine_pools" {
      for_each = var.node
      content {
        cloud_credential_secret_name = data.rancher2_cloud_credential.auth.id
        control_plane_role           = machine_pools.key == "ctl_plane" ? true : false
        etcd_role                    = machine_pools.key == "ctl_plane" ? true : false
        name                         = machine_pools.value.name
        quantity                     = machine_pools.value.quantity
        worker_role                  = machine_pools.key != "ctl_plane" ? true : false

        machine_config {
          kind = rancher2_machine_config_v2.machineconfig[machine_pools.key].kind
          name = replace(rancher2_machine_config_v2.machineconfig[machine_pools.key].name, "_", "-")
        }
      } # End of dynamic for_each content
    }   # End of machine_pools
  }
}

# creating a machine config to be used while creating the cluster

resource "rancher2_machine_config_v2" "machineconfig" {
  for_each      = var.node
  generate_name = "${each.value.name}-config"

  vsphere_config {
    cfgparam      = ["disk.enableUUID=TRUE"] # Disk UUID is Required for vSphere Storage Provider ( mandatory for the cluster to work )
    clone_from    = var.vsphere_env.cloud_image_name
    cloud_config  = file("/root/terraform/cloud.yaml", )
    cpu_count     = each.value.cpu
    creation_type = "template"
    datacenter    = var.vsphere_env.datacenter
    datastore     = var.vsphere_env.datastore
    disk_size     = each.value.disk_size
    memory_size   = each.value.ram
    network       = var.vsphere_env.vm_network
    folder        = var.vsphere_env.folder
    pool          = var.vsphere_env.pool
  }
}

Edit: This post has been updated to reflect changes in newer versions of Rancher.

Note: As mentioned by Jonathan in the comments, disabling cloud-init's initial network configuration is recommended. To do this, create a file:

/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg

To contain:

network: {config: disabled}

In your VM template.

How networking configuration is applied to k8s nodes (or VM's in general) in on-premises environments is usually achieved by one of two ways – DHCP or static. For some, DHCP is not a popular option and static addresses can be time-consuming to manage, particularly when there's no IPAM feature in Rancher. In this blog post I go through how to leverage vSphere Network Protocol Profiles in conjunction with Rancher and Cloud-Init to reliably, and predictably apply static IP addresses to deployed nodes.

50-cloud-init.yaml

/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg