Engineering Build Notes #3: When 200Gi Was More Storage Than the Nodes NeededHow measuring Kubernetes node storage usage led to right-sizing EKS root volumes from 200Gi to 80Gi without under-sizing capacity10 min read·adedamolaajibola.hashnode.devSep 15
Engineering Build Notes #2: When an Idle Kubernetes Cluster Still Couldn't ConsolidateHow right-sizing Kubernetes resource requests improved scheduling flexibility and reduced an Amazon EKS cluster from 5 nodes to 4.8 min read·adedamolaajibola.hashnode.devSep 13
Engineering Build Notes #1: Why Bigger EC2 Instances Reduced Our AWS CostsCost optimization in Amazon EKS isn't always about smaller instances. Here's how metrics led to a cheaper, healthier Kubernetes cluster.5 min read·adedamolaajibola.hashnode.devJul 9
Engineering Debug Diaries #1: The ImagePullBackOff That Wasn't KubernetesA GitHub Actions output bug caused an ImagePullBackOff. Here's how I traced the issue and fixed the CI/CD pipeline.5 min read·adedamolaajibola.hashnode.devJun 27
The EKS 1.32 1.33 Upgrade That Broke Everything (And How I Fixed It)Introduction Upgrading Kubernetes should be boring. This one wasn’t. I recently upgraded a production Amazon EKS cluster from 1.32 to 1.33, expecting a routine change. Instead, it triggered a cascading failure: Nodes went NotReady Add-ons stalled i...4 min read·adedamolaajibola.hashnode.devDec 26, 2025