A sanitized log from a day spent putting ingress in front of the same service two different ways, disproving a "CLI bug" that turned out to be a stale artifact, and wiring open-source analytics into a static site. The specifics are private; the patterns are the point.
A sanitized log from a day split between site automation, cloud-provider edge cases, certificate tooling, and a noisy gateway investigation. The details are private; the useful parts are the patterns.
An experiment: a daily, public log of what I worked on — stripped down to the parts that are actually transferable. No customer names, no internal ticket numbers, just the engineering lessons that survive being taken out of context.
Today had three things worth writing down.
Another sanitized log — the transferable parts of a day that was mostly "where exactly does this run, and is the thing I think is fixed actually fixed?". Four lessons worth keeping.
When you see too many open files in a containerized app, it’s tempting to jump straight to ulimit -n. Sometimes that’s correct. But on Linux (especially with Go apps using fsnotify), the error can also be caused by inotify limits—even if your process has a huge file-descriptor limit.
This post is a practical, copy/paste-friendly checklist to debug the problem on a real Kubernetes cluster.
This tutorial is a guide on how to deploy an application in Kubernetes that will authenticate using Azure Workload Identity on Azure Kubernetes Services (AKS).
This tutorial contains a working example of exposing TCP services (LDAP/LDAPS + SSH) from a single-node k3s cluster running on an EC2 instance, using:
TCPRouteHTTPRoute/GRPCRoute (example file included)The key implementation detail for k3s-on-EC2 with the default overlay networking (flannel): use instance targets + NodePorts for L4 routes. ClusterIP + pod IP targets won’t work unless pods are VPC-routable (AWS VPC CNI).
In this tutorial we deploy a PostgresSQL database in Kubernetes cluster.
The Wikipedia definition should be sufficient in explaining what the software does:
Pi-hole or Pihole is a Linux network-level advertisement and Internet tracker blocking application which acts as a DNS sinkhole and optionally a DHCP server, intended for use on a private network
I wanted to deploy it for a few reasons:
This post is here to explain how was able to deploy PiHole on Kubernetes and how I resolved some of the problems that occurred during the deployment process.
One of our largest customer recently had a problem loading a list of resources from our web application. The problem was a blocker for the customer and required to identify the problem and provide a workaround, if possible. I was assigned the task as I was the SME in this area (NodeJS microservices, infrastructure such as storage, microservice messaging and configuration).