3. 3
Advantages of k3s
• Small binary size (<50M)
• Low memory consumption
• Multi-arch support
‒ Pre-compiled ELF binaries for x86_64, arm64 and armv7(32bit)
• It’s suitable for EDGE/IOT Computing
• Installation is simple
‒ https://github.com/rancher/k3s/blob/master/README.md
• Build
‒ dapper + docker (Alpine Linux) [* see scripts/release.sh]
• Reference
‒ https://k3s.io/
‒ https://github.com/rancher/k3s/
4. 4
Differences to k8s
• All k8s Alpha features have been removed.
• Container runtime
‒ Default: Containerd
• Datastore
‒ SQLite is embedded. (Optional: etcd, PostSQL,
MySQL,DQLite..)
• Ingress controller
‒ Traefik (Switching back to nginx?)
• etc
5. 5
My experiment: A k3s cluster on Pis
• 1 master node: x86_64 [linux-8mug]
‒ OS: OpenSUSE Tumbleweed [ver:20191204]
• 3 worker nodes: aarch64 [pi4b + pi3b+] + armv7 [pi2b]
‒ OS: OpenSUSE Tumbleweed port images for Raspberry
Pi2/3/4 [ver: 20200207]
6. 6
My experiment: A k3s cluster on Pis
• 1 master node: x86_64 [linux-8mug]
‒ OS: OpenSUSE Tumbleweed [ver:20191204]
• 3 worker nodes: aarch64 [pi4b + pi3b+] + armv7 [pi2b]
‒ OS: OpenSUSE Tumbleweed port images for Raspberry
Pi2/3/4 [ver: 20200207]
7. 7
My experiment: A k3s cluster on Pis
• Deploy 4 replicas of nginx daemons on this hybrid k3s
cluster