bci2: Allow running on a Raspberry Pi

In order to keep "big" applications that just happen to have arm64
container images, like Argo CD and Jenkins, from running on Raspberry
Pis instead of VMs, I added a `du5t1n.me/machine=raspberrypi:NoExecute`
taint to them.  This requires any workload that should be allowed to run
on a Raspberry Pi to explicitly indicate as much.  Since the point of
adding *k8s-aarch64-n1.pyrocufflink.blue* to the cluster was to be able
to build container images, the pod template for container image jobs
needs to include this toleration.
bci2-resources
Dustin 2023-10-28 09:58:47 -05:00
parent a4e9602ca9
commit 14cb41d4d9
1 changed files with 4 additions and 0 deletions

View File

@ -17,3 +17,7 @@ spec:
limits: limits:
github.com/fuse: 1 github.com/fuse: 1
hostUsers: false hostUsers: false
tolerations:
- key: du5t1n.me/machine
value: raspberrypi
effect: NoExecute