The Kubernetes Elephant in the Room

When I wrote the first architecture proposal to run Kubernetes at scale at Citigroup in 2016, I encountered the dilemma of this meme. I decided not to address the elephant in the room, and I explained the consequences of this decision here.

On this day, two years ago, I made the pivotal decision to join StormForge, a move I made to tackle this very problem.

Nowadays, besides writing controllers, I dedicate my time to educating folks about how fundamental and critical this Kubernetes primitive - requests - is for cloud costs and performance.

StormForge is purpose-built for Kubernetes.

I invite my LinkedIn network to try it — it is free for 30 days.

Or, drop me a DM, and we will register your clusters together. You will see recommendations in as little as 10 minutes.

Key benefits include:

• Granular visibility & control over Request & Limit settings at Namespace AND Workload levels
• Ability to Gradually apply recommendations, so you can visualize impact in real-time
• Ability to rightsize all workload types WITH BOTH vertical and horizontal autoscalers together
• Guardrails for Dev teams to ensure their Apps are never at risk
• Forecasting-based machine learning recommendations that use months of data to extract seasonality and trends