---
title: "Muhammad Hassaan Javed (@itxcrusher) | Hashnode"
description: "Reducing your cloud bill, therapy bill, & blood pressure all at once! Read the latest articles by Muhammad Hassaan Javed on Hashnode."
url: "https://hashnode.com/@itxcrusher"
---

@itxcrusher

# Muhammad Hassaan Javed

@itxcrusher · Lahore, Pakistan · Joined May 2026

Reducing your cloud bill, therapy bill, & blood pressure all at once!

[Website](https://linktr.ee/itxcrusher)

### [How a do-not-disrupt annotation broke Karpenter consolidation](https://blog.infraforge.agency/how-a-do-not-disrupt-annotation-broke-karpenter-consolidation?utm_source=hashnode&utm_medium=feed)

Our Karpenter cluster went from 108 nodes to 198 over one weekend while pod count barely moved, consolidation fell to about an eighth of its normal rate, and our EC2 on-demand bill jumped 2.2x. The ca

16 min read · [blog.infraforge.agency](https://blog.infraforge.agency/how-a-do-not-disrupt-annotation-broke-karpenter-consolidation?utm_source=hashnode&utm_medium=feed)

[Aug 18](https://hashnode.com/posts/how-a-do-not-disrupt-annotation-broke-karpenter-consolidation/6a844ce8bdbcdb71a8955147)

### [Worker drops jobs intermittently: startup race, env drift, schema skew](https://blog.infraforge.agency/worker-drops-jobs-intermittently-startup-race-env-drift-schema-skew?utm_source=hashnode&utm_medium=feed)

If your worker is dropping jobs intermittently, sometimes crashing at boot with 'Error 111 connecting to redis:6379. Connection refused' and sometimes producing an empty result.json with no error at a

18 min read · [blog.infraforge.agency](https://blog.infraforge.agency/worker-drops-jobs-intermittently-startup-race-env-drift-schema-skew?utm_source=hashnode&utm_medium=feed)

[Aug 10](https://hashnode.com/posts/worker-drops-jobs-intermittently-startup-race-env-drift-schema-skew/6a794a89669dfbf5c8f24cac)

### [How a missing S3 gateway endpoint route quintupled our NAT bill](https://blog.infraforge.agency/how-a-missing-s3-gateway-endpoint-route-quintupled-our-nat-bill?utm_source=hashnode&utm_medium=feed)

The finance lead asked why AWS charged us $2,100 for NAT gateway data processing last month. Our normal was around $400. Nothing in the release calendar explained it: no new services, no traffic bump

11 min read · [blog.infraforge.agency](https://blog.infraforge.agency/how-a-missing-s3-gateway-endpoint-route-quintupled-our-nat-bill?utm_source=hashnode&utm_medium=feed)

[Jul 16](https://hashnode.com/posts/how-a-missing-s3-gateway-endpoint-route-quintupled-our-nat-bill/6a587149388b49190d4ee894)

### [How one stuck PDB doubled our EKS autoscaler bill in six days](https://blog.infraforge.agency/how-one-stuck-pdb-doubled-our-eks-autoscaler-bill-in-six-days?utm_source=hashnode&utm_medium=feed)

The EC2 bill for our EKS cluster went from $4,200 to about $8,600 over six days, against the same six days the month before. Same cluster, no launch, no traffic event, no team asking for headroom. kub

15 min read · [blog.infraforge.agency](https://blog.infraforge.agency/how-one-stuck-pdb-doubled-our-eks-autoscaler-bill-in-six-days?utm_source=hashnode&utm_medium=feed)

[Jul 16](https://hashnode.com/posts/how-one-stuck-pdb-doubled-our-eks-autoscaler-bill-in-six-days/6a58518845ac8f203278f6c6)

### [Recovering a status page from a half-finished schema migration](https://blog.infraforge.agency/recovering-a-status-page-from-a-half-finished-schema-migration?utm_source=hashnode&utm_medium=feed)

The log line was 'database schema version 23 is dirty, refusing to start' and the pod exited immediately after printing it. The team had already tried a Helm rollback to the previous chart version. Th

15 min read · [blog.infraforge.agency](https://blog.infraforge.agency/recovering-a-status-page-from-a-half-finished-schema-migration?utm_source=hashnode&utm_medium=feed)

[Jul 13](https://hashnode.com/posts/recovering-a-status-page-from-a-half-finished-schema-migration/6a54fc8263a30a708fa3b6cd)
