Creating the VM on a bridged network on VMware vSphere-air-gapped environment

Execute this procedure on the air-gapped tools-system.
  • Use the Assets VM ISO image generated by in the Creating the VMware Assets VM Image step.
  • Use the Talos machine config file generated in the Generating the Talos Machine Configuration Files step for user-data.
  • You do not need to create a storage disk on the VM.
  • After deploying the VM using the OVA image:
    • Increase the number of vCPUs to 4.
    • Increase the memory to 16G.
    • Increase the main disk size to 300G. On boot, Talos automatically extends the file system.
    • Enable 100% resource reservation for the CPU, memory and disk.
  1. Download and install the latest version of the VMware OVF Tool from the VMware Developer website.
  2. Display details about the OVA image.
    $ ovftool vmware-amd64.ova 
    OVF version:   1.0 
    VirtualApp:    false 
    Name:          talos 
     
    Download Size:  104.05 MB 
    
    Deployment Sizes: 
      Flat disks:   8.00 GB 
      Sparse disks: Unknown 
    
    Networks: 
      Name:        VM Network 
      Description: The VM Network network 
    
    Virtual Machines: 
      Name:               talos 
      Operating System:   other3xlinux64guest 
      Virtual Hardware: 
        Families:         vmx-15 
        Number of CPUs:   2 
        Cores per socket: automatic 
        Memory:           2.00 GB 
     
        Disks: 
          Index:          0 
          Instance ID:    4 
          Capacity:       8.00 GB 
          Disk Types:     SCSI-VirtualSCSI 
     
        NICs: 
          Adapter Type:   VmxNet3 
          Connection:     VM Network 
     
    Properties: 
      Key:         talos.config 
      Label:       Talos config data 
      Type:        string 
      Description: Inline Talos config 
     
    References: 
      File:  disk.vmdk 
  3. Create a base64 encoded hash from the Talos machine configuration for the node.
    In this example, the output is stored as an environment variable to make it easy to use in the command to deploy the image using the OVF Tool.
    export NODECONFIG=$(base64 -i eda-assets.domain.tld.yaml)
  4. Deploy the OVA image using the OVF Tool.

    For details about command line arguments, see the OVF Tool documentation from the VMware website.

    ovftool --acceptAllEulas --noSSLVerify \ 
     -dm=thin \ 
     -ds=DATASTORE \ 
     -n=eda-assets \ 
     --net:"VM Network=OAM" \ 
     --prop:talos.config="${NODECONFIG}" \ 
    eda-asset-vm-vmware-amd64.ova \ 
    vi://administrator%40vsphere.local@vcenter.domain.tld/My-DC/host/My-Cluster/Resources/My-Resource-Group
    This step deploys the VM with the CPU, memory, disk, and NIC configuration of the default OVA image. The next step updates these settings.
  5. In vCenter, edit the VM settings.
    Make the following changes:
    • Increase the number of vCPUs to 4.
    • Increase the memory to 16G.
    • Increase the main disk size to 300G. On boot, Talos automatically extends the file system.
    • Enable 100% resource reservation for the CPU, memory and disk.
  6. Power on the virtual machine.