Please refer to the following until node's live-os booting:
https://itnext.io/okd-4-5-single-node-cluster-on-windows-10-using-hyper-v-3ffb7b369245
I haven't tried, though, and I guess this method is also enable to setup bootstrap server.
-
Boot live-os of CoreOS with Fedra CoreOS ISO.
-
At the first of booting live-os, add kernel command line in GRUB edit screen.
ip=192.168.122.22::192.168.122.4:255.255.255.0:worker-1:bond0:none bond=bond0:eth0,eth1:mode=active-backup nameserver=192.168.122.4The first parameter is IP address to set to bonding interface, and then this will be set to bridge IF of OVNKubernetes node via OKD installation. About each parameter of Dracut kernel arguments' details refer below: https://docs.fedoraproject.org/en-US/fedora-coreos/sysconfig-network-configuration/#_via_kernel_arguments
-
Once booted live-os, confirm if the bonding interface is correct.

-
Execute
coreos-installwith--copy-network.
(On my environment, the load balancer of API servers is simultaneously a web server for providing ignition files.) -
Before doing reboot, change hostname of node.
[core@worker-2 ~]$ sudo -i [root@worker-2 ~]# mkdir sda4 [root@worker-2 ~]# mount /dev/sda4 sda4 [root@worker-2 ~]# chroot sda4/ostree/boot.1/fedora-coreos/*/0/ [root@worker-2 ~]# echo $HOSTNAME > sda4/ostree/boot.1/fedora-coreos/*/0/etc/hostname [root@worker-2 ~]# umount sda4 [root@worker-2 ~]# reboot -
And then do the same procedure with one that appeared from the community step by step.
The cluster built with this tip needs to make sure correct condition via even upgrading node.

