interestingsoup/urbit-aarch64 is the image used in this tutorial. Learn more about why and how we made it here

This guide assumes you have:

• Setup a persistent volume and presistent volume claim for your Urbit pod. I am providing my pv.yaml and pvc.yaml as an example.
• Installed a LoadBalancer service on your cluster, I am using MetalLb.

The docker image being used executes urbit upon running, so you only need to supply thr args. When setting args in *-planet.yaml you may referrence the Urbit man page example:

Simple Usage:
   urbit -c <my-comet> to create a comet (anonymous urbit)
   urbit -w <my-planet> -k <my-key-file> if you own a planet
   urbit <my-planet or my-comet> to restart an existing urbit

Modify new-planet.yaml with your information before running the command below.

$kubectl apply -f new-planet.yaml -n urbit

You can check log output of the pod to see if any error occurs once the Urbit container is created:

$kubectl logs <pod_name> -n urbit

After your planet is successfully launched, the pod should error out. This is normal

You can see your pod error by running: kubectl get pods -A

Once the pod errors out, you can go ahead and delete your deployment:

$kubectl delete -f new-planet.yaml -n urbit

Lastly, apply restart-planet.yaml to restart an existing planet.

$kubectl apply -f restart-planet.yaml -n urbit

You should now see your Urbit pod up and running: kubectl get pods -A. You can see Urbit service has successfully started by view pod logs: kubectl logs <pod_name> -n urbit In the pod logs look out for live and ames port that Urbit is using, you will use these ports in service.yaml

$kubectl exec -it <pod_name> -n <namespace> -- curl -s -X POST -H "Content-Type: application/json" \
    -d '{ "source": { "dojo": "+code" }, "sink": { "stdout": null } }' \
    http://127.0.0.1:12321

It should out put something like this: "rander-suolus-guspod-wacel\n". That is your access code, be sure to exclude the \n at the end.

Apply service.yaml after you have configured it with your settings. I am using MetalLB as my LoadBalancer. It assigns an external IP to my service allowing it to be accessed outside the node. In service.yaml replace the target ports with ports you saw being used in kubectl logs <pod_name> -n urbit command from the previous step.

$kubectl apply -f service.yaml -n urbit

Run kubectl get svc -A and look for the service that was created for Urbit.

NAMESPACE       NAME                   TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)                        AGE
urbit           urbit                  LoadBalancer   10.43.5.99      192.168.4.210   80:32432/TCP,38254:30582/TCP   19h

As you can see from my output above, I now have an ExternalIP assigned and if I go to that IP on any device on my network, I can access Urbit Landscape successfully.

Urbit group: web+urbitgraph://group/~togtun-pocres/brain-interestingsoup-bowl-with-spoon
Urbit DM: ~togtun-pocres
Website: InterestingSoup.com
TikTok?! Why Not!: @interestingsoup

~nartec-tinrus: for working alongside me to create this and also supplying a planet to make testing easier!