We now have a beautiful cluster assembled and running, but no software running on it yet. So let's get started and provision Kubernetes on top of it so we can manage our nodes easier!
For our Kubernetes setup we want a lightweight Kubernetes installation seeing the required Edge computation. For this, we can utilize K3S which is a distribution built specifically to run on IoT & Edge devices.
Personally, the installation feels similar to how we installed and configured Docker Swarm before. Install it everywhere and join nodes to the master - quick and easy!
Installing K3S is super trivial! There is however an easier way if you want to automate all of it, by utilizing the CLI and adding just 1 parameter.
Master Node Setup
To configure our Master Node, we execute the following command that will pass the secret we define:
curl -sfL https://get.k3s.io | sh -s server --cluster-init --token "XAVIER_HIS_SECRET_TOKEN" --write-kubeconfig-mode 644
💡 As you may have noticed, we are utilizing
--write-kubeconfig-mode 644to allow our cluster to be imported in rancher later.
Worker Node Setup
Finally, we can add our Worker (or Agent) nodes by running the following line on each of the nodes:
curl -sfL https://get.k3s.io | sh -s agent --server https://MASTER_NODE_IP_ADDRESS:6443 --token "XAVIER_HIS_SECRET_TOKEN"
When we now execute
sudo k3s kubectl get nodes -w on our master node, we will see our nodes appearing.
Installing and Configuring Kubectl
⚠ Execute this on your local machine! (WSL in this case)
Since we now have a Kubernetes cluster running, it is time to configure it to run on our local system. For that I am utilizing the
Windows Subsystem for Linux system as explained in a previous article.
To install WSL we execute the following:
# Download Kubectlcurl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"# Install itsudo install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl# Verifykubectl version --client
Now this is installed, we can configure it towards our remote cluster:
# Copy over the Kubeconfig file to our local machinescp email@example.com:/etc/rancher/k3s/k3s.yaml nvidia-node-1-config.yaml# Replace localhost with the location of the master nodesed -ie s/127.0.0.1/xavier-nvidia-node-1.local/g nvidia-node-1-config.yaml# Verify that it workskubectl --kubeconfig nvidia-node-1-config.yaml get pods -A# Then copy it over to kubectl directory and activate it# we can now run kubectl get pods -Acp nvidia-node-1-config.yaml ~/.kube/config
Agent does not want to join
Sometimes an agent does not want to join, in that case try utilizing the IP address directly.
⚠ In case something happened, you can uninstall K3S with the following commands:
# Uninstall Server Node/usr/local/bin/k3s-uninstall.sh# Uninstall Agent Node/usr/local/bin/k3s-agent-uninstall.sh
We have now set-up our Nvidia Jetson nodes and are running a Kubernetes cluster on it! To keep this article light, I have decided to move the demonstration to a new article where you will learn to run Dapr as your distributed application runtime as well as Grafana to monitor your nodes