Differences

This shows you the differences between two versions of the page.

--- raspberry [2022/10/05 07:02] – [Kubernetes (k8s) on RaspberryPi] skipidar
+++ raspberry [2023/03/29 06:56] (current) – [Remote install of image per ssh] skipidar
@@ Line 693: / Line 693: @@
-=== Install OS ===
+=== Install OS Raspberry ===
+https://360techexplorer.com/install-k3s-on-raspberry-pi/
+=== Install OS Ubuntu ===
 Use Ubuntu Server 22.04.1. The Current LTS version.
@@ Line 881: / Line 889: @@
 root        6150 53.9 52.2 1250788 484324 ?      Ssl  06:46   8:15 /usr/local/bin/k3s server
 pi          9717  2.0  0.1   6420  1824 pts/0    S+   07:01   0:00 grep --color=auto 6150
+pi@pi2:~$ ls /usr/local/bin/
+crictl  ctr  k3s  k3s-killall.sh  k3s-uninstall.sh  kubectl
 </sxh>
 ==Attach worker nodes to master==
+On k8s server / mater - get teh token
 <code>
-# On a different node run the below command.
 # NODE_TOKEN comes from /var/lib/rancher/k3s/server/node-token on your server
-sudo k3s agent --server https://myserver:6443 --token ${NODE_TOKEN}
+sudo cat /var/lib/rancher/k3s/server/node-token
 </code>
+<sxh shell>
+pi@pi2:~$ sudo cat /var/lib/rancher/k3s/server/node-token
+T10eb2811f7856b5895acac5179c6ae29787957f5289bb00737cf144ac58da851c4::server:9acae609ca530528b4bcc3219720705b
+</sxh>
+Figure out the ip of your server
+<code>
+ip a
+</code>
+The **eth0** adapter is relevant for me.
+<sxh shell>
+pi@pi2:~$ ip a
+: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+    inet 127.0.0.1/8 scope host lo
+       valid_lft forever preferred_lft forever
+    inet6 ::1/128 scope host
+       valid_lft forever preferred_lft forever
+: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
+    link/ether b8:27:eb:c8:d0:18 brd ff:ff:ff:ff:ff:ff
+    inet 192.168.191.32/24 metric 100 brd 192.168.191.255 scope global dynamic eth0
+       valid_lft 82237sec preferred_lft 82237sec
+    inet6 fe80::ba27:ebff:fec8:d018/64 scope link
+       valid_lft forever preferred_lft forever
+: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
+    link/ether b8:27:eb:9d:85:4d brd ff:ff:ff:ff:ff:ff
+: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default
+    link/ether 3a:27:9b:9b:d2:5f brd ff:ff:ff:ff:ff:ff
+    inet 10.42.0.0/32 scope global flannel.1
+       valid_lft forever preferred_lft forever
+    inet6 fe80::3827:9bff:fe9b:d25f/64 scope link
+       valid_lft forever preferred_lft forever
+: cni0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default qlen 1000
+    link/ether 2e:80:11:68:72:4e brd ff:ff:ff:ff:ff:ff
+    inet 10.42.0.1/24 brd 10.42.0.255 scope global cni0
+       valid_lft forever preferred_lft forever
+    inet6 fe80::2c80:11ff:fe68:724e/64 scope link
+       valid_lft forever preferred_lft forever
+: vethf8a47774@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
+    link/ether 22:9e:ba:f3:6d:7b brd ff:ff:ff:ff:ff:ff link-netns cni-afc93733-4c10-7c13-e702-e2159f2115e0
+    inet6 fe80::209e:baff:fef3:6d7b/64 scope link
+       valid_lft forever preferred_lft forever
+: veth4dd4db4c@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
+    link/ether 92:68:4b:e9:89:af brd ff:ff:ff:ff:ff:ff link-netns cni-520c6f0a-d043-1c4e-10cd-1877f56186fa
+    inet6 fe80::9068:4bff:fee9:89af/64 scope link
+       valid_lft forever preferred_lft forever
+: veth82490627@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
+    link/ether 92:49:38:ab:7a:a6 brd ff:ff:ff:ff:ff:ff link-netns cni-69a4e084-4fd7-25df-0237-d034c7549c13
+    inet6 fe80::9049:38ff:feab:7aa6/64 scope link
+       valid_lft forever preferred_lft forever
+: veth99adcc15@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
+    link/ether f2:a9:ea:60:33:79 brd ff:ff:ff:ff:ff:ff link-netns cni-d01d4a95-b65c-54c4-76c2-0752a4639660
+    inet6 fe80::50b3:2bff:fe69:7914/64 scope link
+       valid_lft forever preferred_lft forever
+: veth748d4e42@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
+    link/ether 32:16:9b:b6:f4:9f brd ff:ff:ff:ff:ff:ff link-netns cni-099b5741-6df4-3801-6694-a6357459a63d
+    inet6 fe80::3016:9bff:feb6:f49f/64 scope link
+       valid_lft forever preferred_lft forever
+</sxh>
+On a different node run the below command.
+<code>
+export K3S_KUBECONFIG_MODE="644"
+export K3S_URL="https://192.168.191.32:6443"
+export K3S_TOKEN="T10eb2811f7856b5895acac5179c6ae29787957f5289bb00737cf144ac58da851c4::server:9acae609ca530528b4bcc3219720705b"
+curl -sfL https://get.k3s.io | sh -
+</code>
+==== Remote install of image per ssh ====
+see
+https://weberblog.net/reinstall-your-raspberry-over-the-network/
+  * Login via SSH to the system on which the image is located and read it via dd. The stdout is tunneled through SSH to the local system.
+  * Using pv you can see how much data is transferred. (You may need to install it with apt-get, but you can also omit this.)
+  * funzip extracts the first file and sends it to stdout.
+  * dd writes it to the SD-card.
+<code>
+#This will enable the reset of the Raspberry without regular commands.
+echo 1 > /proc/sys/kernel/sysrq
+#download image
+curl -L http://downloads.raspberrypi.org/raspbian_lite_latest | funzip | dd bs=4M of=/dev/mmcblk0
+# restart the pi (Sofortiger Neustart des Systems (ohne Synchronisation der Speichermedien!))
+echo b > /proc/sysrq-trigger
+</code>