---
title: "Adedamola Ajibola (@Adedamolaajibola) | Hashnode"
description: "DevOps tinkerer | Cloud enthusiast | Technical writer | Volunteering advocate"
url: "https://hashnode.com/@Adedamolaajibola"
---

@Adedamolaajibola

# Adedamola Ajibola

@Adedamolaajibola · Lagos, Nigeria · Joined July 2022

### [Engineering Build Notes #3: When 200Gi Was More Storage Than the Nodes Needed](https://adedamolaajibola.hashnode.dev/engineering-build-notes-3-when-200gi-was-more-storage-than-the-nodes-needed?utm_source=hashnode&utm_medium=feed)

How measuring Kubernetes node storage usage led to right-sizing EKS root volumes from 200Gi to 80Gi without under-sizing capacity

10 min read · [adedamolaajibola.hashnode.dev](https://adedamolaajibola.hashnode.dev/engineering-build-notes-3-when-200gi-was-more-storage-than-the-nodes-needed?utm_source=hashnode&utm_medium=feed)

[Sep 15](https://hashnode.com/posts/engineering-build-notes-3-when-200gi-was-more-storage-than-the-nodes-needed/6aa8ade5a029167966e1ea08)

### [Engineering Build Notes #2: When an Idle Kubernetes Cluster Still Couldn't Consolidate](https://adedamolaajibola.hashnode.dev/engineering-build-notes-2-when-an-idle-kubernetes-cluster-still-couldn-t-consolidate?utm_source=hashnode&utm_medium=feed)

How right-sizing Kubernetes resource requests improved scheduling flexibility and reduced an Amazon EKS cluster from 5 nodes to 4.

8 min read · [adedamolaajibola.hashnode.dev](https://adedamolaajibola.hashnode.dev/engineering-build-notes-2-when-an-idle-kubernetes-cluster-still-couldn-t-consolidate?utm_source=hashnode&utm_medium=feed)

[Sep 13](https://hashnode.com/posts/engineering-build-notes-2-when-an-idle-kubernetes-cluster-still-couldn-t-consolidate/6aa63daf30d78e2f1ec0ac42)

### [Engineering Build Notes #1: Why Bigger EC2 Instances Reduced Our AWS Costs](https://adedamolaajibola.hashnode.dev/engineering-build-notes-1-why-bigger-ec2-instances-reduced-our-aws-costs?utm_source=hashnode&utm_medium=feed)

Cost 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.dev](https://adedamolaajibola.hashnode.dev/engineering-build-notes-1-why-bigger-ec2-instances-reduced-our-aws-costs?utm_source=hashnode&utm_medium=feed)

[Jul 9](https://hashnode.com/posts/engineering-build-notes-1-why-bigger-ec2-instances-reduced-our-aws-costs/6a4ef2c6ed6180b67a84a37f)

### [Engineering Debug Diaries #1: The ImagePullBackOff That Wasn't Kubernetes](https://adedamolaajibola.hashnode.dev/engineering-debug-diaries-1-the-imagepullbackoff-that-wasn-t-kubernetes?utm_source=hashnode&utm_medium=feed)

A 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.dev](https://adedamolaajibola.hashnode.dev/engineering-debug-diaries-1-the-imagepullbackoff-that-wasn-t-kubernetes?utm_source=hashnode&utm_medium=feed)

[Jun 27](https://hashnode.com/posts/engineering-debug-diaries-1-the-imagepullbackoff-that-wasn-t-kubernetes/6a4ef479b11b33cedc34be5a)

### [The EKS 1.32 1.33 Upgrade That Broke Everything (And How I Fixed It)](https://adedamolaajibola.hashnode.dev/the-eks-132-133-upgrade-that-broke-everything-and-how-i-fixed-it?utm_source=hashnode&utm_medium=feed)

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.dev](https://adedamolaajibola.hashnode.dev/the-eks-132-133-upgrade-that-broke-everything-and-how-i-fixed-it?utm_source=hashnode&utm_medium=feed)

[Dec 26, 2025](https://hashnode.com/posts/the-eks-132-133-upgrade-that-broke-everything-and-how-i-fixed-it/694eb0783f0fc9e7279c249e)
