This tutorial how to setup WIFI on the master pi to connect to different WLAN
Also the Kubedge team went through the process, it has not been documented yet. Still some example files are available bellow.
Install dhcpcd5. The dhcpcd service controls the start of the interfaces as well as the creation of the /etc/resolv.conf
sudo apt-get install dhcpcd5
The /etc/dhcpcd.conf (not the /etc/dhcpd/dhcpd.conf) controls the startup of the interfaces. We want the eth0 to be kind of static, the wlan0 to be dynamic
diff dhcpcd.conf /home/pirate/proj/kubedge/kube-rpi/config/cluster1/hypriotos/kubemaster-pi/etc/dhcpcd.conf
You can keep 3 files in the /etc/network/interfaces.d: l0, eth0 and wlan0. Note comment out the iptables line at first in the eth0 file. eth0 is static so that the internal IP of the master PI is always 192.168.2.1
diff lo /home/pirate/proj/kubedge/kube-rpi/config/cluster1/hypriotos/kubemaster-pi/etc/network/interfaces.d/lo diff eth0 /home/pirate/proj/kubedge/kube-rpi/config/cluster1/hypriotos/kubemaster-pi/etc/network/interfaces.d/eth0
In wlan0 the list of the sssid you want to potentially connect to. Needs to match the id_str in the wpa_supplicant.conf
vi wlan0 vi /etc/wpa_supplicant/wpa_supplicant.conf
Check the IP address. Depending on PI3B or PI3B+, the WLAN network may be different. Use the files in $HOME/proj/kubedge/kube-rpi/config/cluster1/hypriotos/ as examples.
ip a iwconfig sudo ip link set wlan0 up sudo iwlist scan | grep ES sudo iwlist scan | grep ED wpa_passphrase <sommessid> sudo vi /etc/network/interfaces.d/wlan0 sudo vi /etc/wpa_supplicant/wpa_supplicant.conf sudo systemctl restart dhcpcd
At that point the wlan0 should come up and IP 192.168.2.1 should be assigned to the master-pi.
At that point you should be able to unplug the eth0 cable, reboot the PI and check in your router for a kubemaster-pi and ssh into the node. It should allow you access the kubemaster-pi using WIFI.