Join us

On How We Moved to Kubernetes

Migrating from AWS ECS to AWS EKS? Beats the bark out of those pesky spot instance disruptions, but introduces a new player: the complexity monster named Kubernetes. Bigger, faster, cheaper—if you know the dance steps.

Juggling CPUs in Kubernetes feels like herding caffeinated cats. Enter Karpenter to save on costs by cherry-picking instances—though it turns out not all CPUs play nice. Unforeseen headaches like restrictive firewall settings and iffy instance type choices took a swing at them, loudly reminding everyone that planning transitions is a must.

Deploying Actions Runner Controller on Kubernetes made CI/CD roll in under budget. And switching to jemalloc axe-murdered memory use by 20%, freeing resources during sleepy traffic hours.


Let's keep in touch!

Stay updated with my latest posts and news. I share insights, updates, and exclusive content.

Unsubscribe anytime. By subscribing, you share your email with @faun and accept our Terms & Privacy.

Give a Pawfive to this post!


Only registered users can post comments. Please, login or signup.

Start writing about what excites you in tech — connect with developers, grow your voice, and get rewarded.

Join other developers and claim your FAUN.dev() account now!

Avatar

The FAUN

FAUN.dev()

@faun
The FAUN watches over the forest of developers. It roams between Kubernetes clusters, code caves, AI trails, and cloud canopies, gathering the signals that matter and clearing out the noise.
Developer Influence
3k

Influence

302k

Total Hits

3711

Posts