knative-pi | Run Knative on Raspberry Pi in 5 minutes

This instructions are based on Ubuntu Post. Configure some environment variables based on your operating system, you can use the template provided. Enter the values based on your Operating system in to the .env file. Load the environment variables.
You will need a 64 bit OS, you can use Ubuntu or Raspberry OS. I will be using Ubuntu 20.10 64bit
Get an application to image the OS into the SD Card, you can use RaspBerry Imager or any other tool. Choose MacOS or Windows
Scroll down and Select Ubuntu Server 20.10 64bit (RPi 3/4/400) (Do not select Desktop)
Select SD Card
WRITE
WAIT for ~10 minutes
Login and change the default password ubuntu to something different. Check if you have a local ssh, if not then create a new one with ssh-keygen. If you have more than one ssh key you can use -i to be sure it picks the correct one. Now you can ssh into the pi without a password. It should print aarch64 to indicate arm64. I recommend to change the hostname of the pi from the default ubuntu before you install kubernetes to something useful like pi4.
Install the k3sup command line tool, check that you have latest version I'm using 0.9.7. Run the following command to install k3s on the pi as a master node. If you ever need to recover the kubeconfig from the cluster you can use the flag --skip-install1.
Install the k3sup command line tool, check that you have latest version I'm using 0.9.7 k3sup version
Run the following command to install k3s on the pi as a master node. source .env k3sup install \ --ip $IP \ --user ubuntu \ --merge \ --local-path $HOME/.kube/config \ --context knative-pi \ --k3s-channel latest \ --k3s-extra-args '--disable=traefik' The --ip specifies the IP Address to ssh in to the pi The --user specifies the user to ssh as The --merge specified to merge the kubeconfig of the new cluster into an existing kubeconfig file The --local-path specifies which file to write the kubeconfig file, in our case specify an existing one to merge in the new config The --context specifies the context for the cluster when you use kubectl or kn The --k3s-channel specifies which version of kubernetes to install The --k3s-extra-args with --disable=traefik is to avoid the installation of traefik as we are going to use knative networking
If you ever need to recover the kubeconfig from the cluster you can use the flag --skip-install1 source .env k3sup install \ --ip $IP \ --user ubuntu \ --merge \ --local-path $HOME/.kube/config \ --context knative-pi \ --skip-install
I will be using the pre-release build and install instructions.
Install Knative Serving kubectl apply -f https://storage.googleapis.com/knative-nightly/serving/latest/serving-crds.yaml kubectl wait --for=condition=Established --all crd kubectl apply -f https://storage.googleapis.com/knative-nightly/serving/latest/serving-core.yaml kubectl wait pod --timeout=-1s --for=condition=Ready -n knative-serving -l '!job-name'
Install Contour 1.10 that uses arm enable envoy with 1.16 kubectl apply -f https://storage.googleapis.com/knative-nightly/net-contour/latest/contour.yaml kubectl wait --for=condition=Established --all crd kubectl wait pod --timeout=-1s --for=condition=Ready -n contour-external -l '!job-name' kubectl wait pod --timeout=-1s --for=condition=Ready -n contour-internal -l '!job-name'
Install the Knative Network Controller: kubectl apply --filename https://storage.googleapis.com/knative-nightly/net-contour/latest/net-contour.yaml kubectl wait pod --timeout=-1s --for=condition=Ready -n knative-serving -l '!job-name'
To configure Knative Serving to use previous installed Network Controller by default: kubectl patch configmap/config-network \ --namespace knative-serving \ --type merge \ --patch '{"data":{"ingress.class":"contour.ingress.networking.knative.dev"}}'
Set the environment variable EXTERNAL_IP to External IP Address of the Worker Node EXTERNAL_IP="$(kubectl get svc envoy -n contour-external -o=jsonpath='{.status.loadBalancer.ingress[0].ip}')" echo EXTERNAL_IP==$EXTERNAL_IP
Set the environment variable KNATIVE_DOMAIN as the DNS domain using nip.io KNATIVE_DOMAIN="$EXTERNAL_IP.nip.io" echo KNATIVE_DOMAIN=$KNATIVE_DOMAIN Double check DNS is resolving dig $KNATIVE_DOMAIN
Configure DNS for Knative Serving kubectl patch configmap -n knative-serving config-domain -p "{\"data\": {\"$KNATIVE_DOMAIN\": \"\"}}"
Verify that Knative is Installed properly all pods should be in Running state and contour-external service configured. kubectl get pods -n knative-serving kubectl get pods,svc -n contour-external
I have two sample applications in apps/ one for go and one for nodejs.
Install ko version v0.6.0+ from https://github.com/google/ko
Setup your docker registry info, replace the value of DOCKER_HUB_USER export DOCKER_HUB_USER=csantanapr export KO_DOCKER_REPO="docker.io/${DOCKER_HUB_USER}"
change directory to the root of the go app cd apps/helloworld-go
Publish container image for all architecture types including arm64 ko publish --platform=all -B .
Deploy as Knative service kn service create helloworld-go --image ${KO_DOCKER_REPO}/helloworld-go
Run the app curl $(kn service describe helloworld-go -o url)
Install Docker-Desktop with experimental enable follow instructions here https://www.docker.com/blog/multi-arch-images/
Create a new builder if you don't have one already docker buildx create --name mybuilder
Configure your docker registry export DOCKER_HUB_USER=csantanapr
change directory to the root of the go app cd apps/helloworld-nodejs
Build and Push the image docker buildx build \ -t ${DOCKER_HUB_USER}/helloworld-nodejs:latest \ --platform linux/amd64,linux/arm64 \ --push .
Deploy as Knative service kn service create helloworld-nodejs --image docker.io/${DOCKER_HUB_USER}/helloworld-nodejs
Run the app curl $(kn service describe helloworld-nodejs -o url)