How to Run Kubernetes on Raspberry Pi 4 - Ubuntu Server
In this post I just want to write or kind of document how I managed to run Kubernetes on Ubuntu Server image of Raspberry Pi. Just for a short background, I got two Raspberry Pi 4 Model B 4GB as a birthday Gift from my wife and since the first night I started to play with them.
Finding an Image
As you may know, you have to find an image that suits you. In general, Raspbian is the official Operating System of Raspberry Pi but somehow it was not suitable for me since I was looking for something more like server operating system. Thus, I decided to go with Ubuntu Server Image. Creating Installation Media was pretty neat for me since I just followed the documention Raspberry Pi 4 Model B 4GB
Since I have two Raspberry Pi I have done the same thing twice!
Home Network
In General you can have dedicated switch for your Raspberry Pi and connect them into this Switch. However, in my case, I just directly connected them into my router. My home network subnet is 192.168.0.50/32. Take a note of your home address since you will need it for your configuration.
First Boot
YaY! First boot and now I have both my devices up and running. But hey! Wait! I have no Monitor and due to some reason I have no direct access to my router to find the IP Address of the devices. Yes! Right! Too early for googling for a solution but I have no idea so I started to search and I figure out that I can use Address Resolution Protocol aka arp to see the IP Addresses of my local network:
Running above told me that following IPs are my Raspberry Pi:
Now I can SSH into my machines and do the initial setup like a normal Ubuntu Server.
Installing Docker
Docker installation is straight forward and you need to run following:
Enabling CGroup Memory
One of the biggest challenge for me was to enabling CGroup Memory in Ubuntu image of Raspberry Pi. Unlike other normal places for enabling it, in Raspberry Pi Ubuntu’s image you need to append /boot/firmware/nobtcmd.txt and add following:
Note :
I have disabled IPv6 as well to make the setup easier.
Ensure iptables tooling does not use the nftables backend
First, enable iptables Filtering on Bridge Devices:
Apart from that, as per mentioned in documentation of kubernetes , you need to switch the iptables tooling to ‘legacy’ mode to avoid duplicated firewall rules and breaks kube-proxy.
Installing Kubernetes
First lets add the Kubernetes package:
Now is the time to install kubeadm:
Configuring kubeadm
First of all we have to pull image k8s.gcr.io/kube-apiserver:v1.16.3
:
When we need to configure second node?
You have to run all above steps on both Raspberry Pi.
Node 1:
When you initializes a Kubernetes control-plane node, you need to consider assigning a cidr
for your pod by --pod-network-cidr
. It specify range of IP addresses for the pod network. If set, the control plane will automatically allocate CIDRs for every node.
Note :
Do not use your home’s subnet for --pod-network-cidr
because later on when you setting up a flannel, you will end up with having a conflict between flannel IP Range and your home’s network. In my case, I initially used home subnet and then I ended up with having flannel IP Address as 192.168.0.1
which is my Router IP Address. It seems flannel is taking a control of the network by picking the first IP Address from the range.
Once you finish initializing your first node you will get instructed to configure $HOME/.kube/config
as a regular user:
As well as you will get the message like following to see how you can join this cluster:
But hey! Wait we have one more step to do.
Deploy a pod network to the cluster.
As you can see in the message after initialization, You should now deploy a pod network to the cluster:
Above gives you more options but I have already selected Flannel . Thus, I applied it by following:
Above deployment will be deploy network configuration pods into your kube-system
namespace and if you run following you will se the pods:
Node 2:
Now it’s time to join the first node! You just need to copy and paste from the note after initialization on first node:
Now if you run following in your first node you will se the details of your both nodes:
Hope this blog helps you to configure your cluster easier. I will try to write more.