om@omniscient:~/blog$ ls -lt
Notes from the network layer
Things I've built, broken and fixed: Kubernetes, Azure networking, ingress, CI/CD. Mostly the parts that took longer than they should have.
- -rw-r--r-- om 9m How Argo CD actually works, and why I'd pick it again A look under the hood of Argo CD: the GitOps idea, the components, the reconcile loop, the sync options that matter, and an honest comparison with pipeline deploys, Flux and Spinnaker.
- -rw-r--r-- om 17m Designing RoleCraft, a browser-only AWS IAM policy builder Why I built a tool that turns plain sentences into least-privilege IAM roles, and how it works underneath: a static data pipeline over 456 AWS services, a pure TypeScript policy engine, five export formats and a CI that applies every export to an AWS emulator.
- -rw-r--r-- om 6m I fixed a downtime with a downtime An unindexed MongoDB query pinned the CPU at 100%. Killing it didn't work because it kept coming back, so I cut the traffic at the network, fixed the index on a quiet database, and let it back in.
- -rw-r--r-- om 5m One checkbox broke the network, and every route table said it shouldn't have A textbook Azure hub-and-spoke, correct UDRs, a firewall that allowed the traffic, and packets that still vanished. The culprit was one unchecked peering setting.
- -rw-r--r-- om 3m Moving 100+ services from Nginx Ingress to Traefik with zero downtime Why I replaced ingress-nginx with Traefik across two organisations, what got simpler, and what didn't carry over.
- -rw-r--r-- om 3m Docker's bridge network quietly broke my VNet peering AKS pods couldn't reach a Docker Swarm VM over a perfectly healthy VNet peering. The culprit was Docker's own default subnet.
total 6 · subscribe via rss