差分

**[https://www.typea.info/blog/index.php/2020/11/13/mac_ubuntu_microk8s_node_cluster/ クラスタを作成する手順]====Driverを[[VirtualBox]]に変更する====*https://multipass.run/＊現在選択されているドライバを確認する<pre>$ sudo multipass get local.driverhyperkit</pre>*hyperkitでは、ネットワークの公開ができなかったので、ドライバを[[VirtualBox]クラスタを作成する（Virtual Boxを使用)]に変更*https://multipass.run/docs/using-virtualbox-in-multipass-macos<pre>$ sudo multipass set local.driver=virtualbox$ sudo VBoxManage list vmsPassword:"microk8s-vm" {d90718db-3795-4116-825f-cffe4a2f0fea}</pre>====[[VirtualBox]]のNetwork Bridgeを構成する====**https://www.virtualbox.org/manual/ch06.html#network_bridged<pre>$ VBoxManage list bridgedifs | grep ^Name:Name: en0: Wi-Fi (AirPort)Name: en1: Thunderbolt 1Name: bridge0Name: p2p0Name: awdl0Name: llw0 $ sudo VBoxManage modifyvm microk8s-vm --nic2 bridged --bridgeadapter2 en0</pre>*インスタンスを立ち上げて新しいNICの名前（enp0s8)を得る<pre>$ multipass exec microk8s-vm -- ip link | grep DOWN3: enp0s8: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000</pre>*新しいNIC（enp0s8)の設定<pre>＄ multipass exec microk8s-vm -- sudo bash -c "cat > /etc/netplan/60-bridge.yaml" <<EOFnetwork: ethernets: enp0s8: # this is the interface name from above dhcp4: true dhcp4-overrides: # this is needed so the default gateway route-metric: 200 # remains with the first interface version: 2EOF $ multipass exec microk8s-vm -- sudo netplan apply</pre>*ipアドレスを確認<pre>$ multipass exec microk8s-vm -- ip address show dev enp0s8 up 3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 08:00:27:3a:92:dd brd ff:ff:ff:ff:ff:ff inet 192.168.0.40/24 brd 192.168.0.255 scope global dynamic enp0s8 valid_lft 86331sec preferred_lft 86331sec inet6 2402:6b00:3666:5800:a00:27ff:fe3a:92dd/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 266sec preferred_lft 266sec inet6 fe80::a00:27ff:fe3a:92dd/64 scope link valid_lft forever preferred_lft forever</pre>====マルチノードクラスタの構成====*構成コマンドの生成<pre>$ microk8s add-nodeFrom the node you wish to join to this cluster, run the following:microk8s join 10.0.2.15:25000/136ac2967078d5490de2d1a2d3a8bf52 If the node you are adding is not reachable through the default interface you can use one of the following: microk8s join 10.0.2.15:25000/136ac2967078d5490de2d1a2d3a8bf52 microk8s join 192.168.0.40:25000/136ac2967078d5490de2d1a2d3a8bf52</pre>*生成されたコマンドを実行<pre>$ microk8s join 192.168.0.47:25000/1c3d59551648b6da13ccbca9cf1a0fadContacting cluster at 192.168.0.47Waiting for this node to finish joining the cluster. .. delhi:~ hirotoyagi$ kubectl get nodeNAME STATUS ROLES AGE VERSIONjinmu Ready <none> 3d16h v1.19.3-34+a56971609ff35amicrok8s-vm Ready <none> 17s v1.19.3-34+9e8b6537ec8b6f</pre>