If you're running on Hetzner, you might want to update your DNS settings to use some other resolvers. This can problem can manifest if you're trying to resolve DNS names that resolve to your own machines *from inside your own machines*.
Want to wait for some Kubernetes resources and don't want to write a full reconciliation loop/operator? Here's how to hack it.
A quick writeup on the 'deployment spectrum' and it's history, as I see it.
You may not need Flux/ArgoCD or any fancy automated reconciliation loop deployment process just yet! Plain old CI runners work quite well for simple automated deployments (this approach powers this blog right now!).
A step by step guide on how to set up SES with Pulumi
A small exploration and guide (with repo) into exposing SSH to a container in a Pod over port 443 (which is normally used for HTTPS).
I finish up the benchmarking process, and share the results. If you want to find what I actually end up using, the answer is in here!
I describe in detail the YAML and Makefile scripts that power the fio and pgbench based tests that will run on every storage provider I managed to set up
I install even more storage providers -- this time OpenEBS cStor, Jiva, LocalPV hostPath, LocalPV ZFS and LINSTOR
I start installing storage plugins, this time Rook (Ceph) -- which takes a while -- and OpenEBS Mayastor. Read this if you want to read a feel-good underdog system administration story.
Part 1 of my second crack at benchmarking storage providers that scale from hobbyist to enterprise. In this post I go over the setup (the code isn't public just yet) of the dedicated servers I'll be using
Kubernetes upgrade sunday -- A series of posts where I do some maintenance and upgrades on my k8s cluster that sometimes happens on a sunday. This sunday I work on node local DNS caching, kube-router, jaeger, cert-manager, traefik, and containerd
Are there some other compelling ingress controllers for the Kubernetes ecosystem I should consider switching to in 2021?
Service to service communication broke down due to old Kubeconfig being fed to my old version of kube-router.
Moving back to Docker (and enabling rootless containers) after running into issues with Podman
I run a small experiment to figure out what the optimal setting is for pm2.
Improving my security posture with ease by following best practices from a blog post (https://www.simplecto.com/get-more-secure-websites-from-your-traefik-configuration) thanks to thanks to Traefik and Kubernetes. This post is also unintentionally an exploration of the amount of work it takes to switch from Traefik v1 to v2.
Bits and bobs to make working with podman a little easier
A somewhat succinct no-bullshit guide to setting up rootless containers on Arch Linux
Jetstack's cert-manager is one of the most important parts of my k8s cluster and I've waited entirely too long to update it. The path from v0.4.0 to v0.16.0 is grueling but pretty easy thanks to well-built software.