Intro to a k8s homelab

kubectl get nodes -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME home-rpi-1 Ready <none> 6h22m v1.19.2 192.168.1.74 <none> Ubuntu 20.04.1 LTS 5.4.0-1019-raspi containerd://1.3.3-0ubuntu2 home-rpi-2 Ready <none> 6h22m v1.19.2 192.168.1.209 <none> Ubuntu 20.04.1 LTS 5.4.0-1019-raspi containerd://1.3.3-0ubuntu2 home-rpi-3 Ready <none> 6h17m v1.19.2 192.168.1.194 <none> Ubuntu 20.04.1 LTS 5.4.0-1019-raspi containerd://1.3.3-0ubuntu2 home-rpi-4 Ready <none> 6h11m v1.19.2 192.168.1.145 <none> Ubuntu 20.04.1 LTS 5.4.0-1019-raspi containerd://1.3.3-0ubuntu2 home-server-1 Ready master 3d12h v1.19.2 192.168.1.111 <none> Ubuntu 20.

Keep reading...

Creating a cluster container registry cache with Harbor and CRI-O

It’s fun. It only works for CRI-O right now since the mirror requires a /project rather than just a base URL. I mean, you could maybe get fancy with some URI rewrite, but I’m not getting into that today. TLDR Anyway, works like this: Install CRI-O Set /etc/containers/registries.conf to a dummy mirror (for now, I did it the hard way with an existing harbor install, but you can do it like this and save yourself a kubectl drain node + install) helm install harbor.

Keep reading...

What's up?

Couple of things. I got a new server. It’s got 4 HDs with uhh… lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 40 bits physical, 48 bits virtual CPU(s): 16 On-line CPU(s) list: 0-15 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel CPU family: 6 Model: 26 Model name: Intel(R) Xeon(R) CPU X5560 @ 2.80GHz Stepping: 5 CPU MHz: 1761.

Keep reading...