2025-08-16 | #debian #gitlab #homelab
Have you ever wondered about hosting your own apt repository? Looked at all the options and thought they’re woefully complex and hard to piece together? If so, read on! I’ll show you how I managed to host my own on a small server using reprepro and publish to it from GitLab CI.
2024-11-06 | #networking #security
How to configure an Authentik flow to conditionally execute stages based on client IP address.
In simpler terms, how do I not get prompted for 2FA/MFA when I’m at home?
A quick writeup for a longstanding issue I’ve had that’s rendered CephFS-backed PersistentVolumes useless on my home K8S cluster. libceph on worker nodes complains about mons speaking the wrong protocol and that wasn’t a red herring, it was the key to the problem all along.
2023-12-14 | #3d-printing #trident
How to get a DSI display (ribbon cable) display to work with a Raspberry Pi compute module on a Manta M8P.
2023-10-10 | #3d-printing #klipper #trident #voron
Notes on getting the BigTreeTech Manta M8P v2.0 printer MCU flashed and working, plus some clarifying points that should be useful to owners of an M8P v1.0/v1.1 board. Includes some info on how to configure for CANbus and how to get the BigTreeTech EBB SB2209 board flashed and working as well.
2023-07-30 | #k8s #networking
A whirlwind dive into kube LoadBalancer services, and a lesson in how things are not always what they seem.
2023-07-15 | #k8s
ArgoCD Image Updater is a tool that works in concert with ArgoCD to update images automatically in your Kubernetes cluster based on a set of rules. Its primary limitation is it requires you use either Helm or Kustomize to deploy your application, as it uses properties of those tools to update the image.
But since Kustomize is so lightweight, it’s actually straightforward to (ab)use it to make ArgoCD Image Updater work for you.
2023-04-28 | #3d-design #woodworking
In which I design and build a new entertainment center
2022-07-27 | #k8s #prometheus
Up until recently, I was running two separate Prometheus instances – one on a Raspberry Pi, and the other in my k3s cluster using kube-prometheus-stack. I wanted to unify them, ideally to simplify management and version control. The challenge here is in how to manage the scrape targets for out-of-cluster resources.
Thanks to my friend Justin, I was able to use a much more elegant solution.
When deploying kube-prometheus-stack, define additionalScrapeConfigs. Since I deployed via the Helm chart, that would mean doing a helm upgrade each time I needed to change things. Gross.
On my home K3S cluster, I was running into a string of weird DNS issues. Here’s how I ended up fixing it.
example.com and reverse)example.com)example.com provided by Cloudflare and DNSSEC-signed.I was mostly having issues resolving hosts in example.com. For example, if a pod were making a query to look for
foo.example.com, I would see in the PDNS logs queries for: