As the title says - you don’t actually need the gitlab cli to connect to Kubernetes clusters exposed via Gitlab Agent. It is easier (and creates a short-lived token instead a long-lived one!), but it is not required.

I’m using 1Password to store my SSH keys - recently i noticed that the git sign process started to fail

❯ git commit -m "very important change"
fatal: cannot exec '/opt/1Password/op-ssh-sign': No such file or directory
error:
fatal: failed to write commit object

It turns out, that the op-ssh-sign has been moved from /opt/1Password/op-ssh-sign to /usr/share/1password/op-ssh-sign. After editing the ~/.gitconfig to use the new path, it started working again. What’s weird, is that in the “Configure Commit Signing…” popup, the automatic setup still uses the /opt directory. Not sure on which version precisely i got broken, but it is still broken on 1Password for Linux 8.12.24 (81224034)

I’m running an HP Z230 SFF as my little homeserver for the last 5 years. It is not the most powerful, but it was energy-efficient enough, and was doing great for the things I’m running on it, so I kept using it. Recently I noticed that despite being idle, the power usage was higher than normal. Normally the power usage with idle workload oscillates around 25-30W, but it was at nearly 60W. On Proxmox I didn’t see that any VM was using much CPU, so I dug deeper. In top on the host, I noticed that only one core was maxed out, and the process kworker/1:3+usb_hub_wq was using a lot of CPU.

As you might guess by some of my older entries, I’m a fan of Backblaze B2 object storage.

Some time ago I created my first Kubernetes operator using Operator-SDK in Golang. Before that, I had some experience with python pykube/kopf, but these libraries are pretty much abandoned, so I decided to take a look at the “first party” solution.

I wanted to create Backblaze B2 buckets and keys in the cluster, but I noticed that at the time, there weren’t any operators available, so I created my own. It supports creating buckets and keys with ACL. I know - what a diversity of feature from a storage operator

Sometimes you need a better GPU for testing - service offerings like runpod.io or salad cloud is cool, for setup a quick docker container for testing, however currently both runpod and salad are missing the ability to setup some kind of sidecar, which would allow user to setup for example a vpn connection to internal network, so you can access the external container from your secure network and not just directly throught the internet.