TL;DR All Docker-in-Docker (dind) jobs of the pipeline now run on autoscaling AKS runners instead of the few docker-tagged VM runners. Each job runs dind as a GitLab service in a privileged pod. No node changes, no extra VMs, and the CI change was mostly one tag. The problem was queueing. The first job of […]
A couple of months ago I wrote about my adventures with the Kubernetes Gateway API and Cilium: https://enaplo.hu/2026/07/03/deploying-cilium-gateway-api/ If you haven’t read it, the short version is: it should have been easy, it wasn’t, and I ended up running an older Gateway API version together with an experimental TLSRoute CRD because Cilium 1.19.5 still expected
After migrating my Kubernetes cluster from Calico to Cilium, enabling kube-proxy replacement and migrating from ingress-nginx to Cilium Ingress, the final step was moving to the Kubernetes Gateway API. What looked like a straightforward migration turned into several hours of debugging. Hopefully this post saves someone else the same time. Environment My goal was simple:
I’ve been looking for a replacement for Google Photos for a while. My requirements were: I found Immich, which looked perfect, but… initially I tried the official Immich Helm chart. After spending a few hours with it, I eventually decided to abandon it and deploy Immich using plain Kubernetes manifests generated from the official Docker
So, Kubernetes, bare-metal cluster, and the etcd died on one of the control-plane machines after a reboot due to a hardware failure. You can clearly see that the control-plane node is “NotReady” and the log shows: What is the Kubernetes way? Kill that node, create a new node, add this new node to the cluster and that’s