This message was deleted.
# harvester
a
This message was deleted.
b
Ok so let me tell you how we do it. We have multiple vlans that do various things, but first when we config a vm we give it dhcp with a private ip and nat. You could use a virtual mikrotik or something to do this function. All harvester nodes and management also get a private vlan with nat, however we static assign those. When the VM is configured we use the cloud image of whatever linux verison, and a simple cloud init to add ssh key and user. Most have efi available for boot so select tat as well. Here is a simple cloud init that works on a lot of various linux flavors.
Copy code
#cloud-config
users:
  - name: somedude
    shell: /bin/bash
    groups: users, wheel, whatever
    ssh_import_id: None
    lock_passwd: true
    sudo: ALL=(ALL) NOPASSWD:ALL
    ssh_authorized_keys:
      - ssh-rsa AAAAB3NzaC1yc2EAAAABJgBjNZEngrFtSGKgiFYd5rEF7zu+miJh7EYVWCZgq4KsonwWv0x8ftzFjUcwPIEF+aZOLSWm0oHbDQr+hDIXwdkkZZfs0f0p9OOrKupt0BnqRc= rsa-key-20191229-somedude
🙌 1
Form this point oyu have a vm that has an ip you cna login to via ssh, then can do whatever networking you want.
Also not sure the order you are doing things. 1 - Install Harvester Node 2 - Install services such as router/etc 3 - Install rancher for management 4 - Use Rancher to deploy RKE2 using Harvester node driver on harvester node.