Platform Obesity, not Complexity, is killing our platforms

We like to say Kubernetes platforms fail because they’re “too complex”. But complexity isn’t the problem. Platforms fail because they’re obese. They’re bloated with an excess of features, tools, abstractions, and opinions that far exceed an organization’s operational capacity and cognitive load—especially in enterprises, regulated environments, and talent-constrained teams. The cloud-native ecosystem doesn’t help. It hands out sweets constantly: one more controller, one more abstraction, one more “best practice.” Each addition seems harmless in isolation. Saying yes is easy. Saying no is career-limiting: since no-one wants to admit their own reality doesn’t match the industry narrative. The Pluralistic Ignorance is real, yo. The ecosystem rewards addition, not subtraction. Often, “simplification” efforts often do the opposite—layering abstractions on top of abstractions until the platform is heavier, slower, and harder to operate and change than before. Eventually, the platform collides with reality: finite talent, finite attention, finite time. Cognitive load exceeds capacity. Operational friction grows. Engineering quality cracks. Business outcomes stall. ROI quietly evaporates. This isn’t a tooling failure. It’s a constraint failure. So how do you fix an obese platform? The same way you fix obesity: by creating a calorie deficit, rigorous exercise and discipline. In the platform world, that means recognizing constraints and designing for and staying within those limits, across technology, processes, organizational culture, budget, engineering skills, team cognitive load and more. Dare to play the hard ’less is more’ subtraction game, not the easy game of addition: treat dealing with constraints, subtraction, prioritization and trade-offs as first-class engineering skills—not as signs of lack of ambition.

Transcript

1. PLATFORM OBESITY J O E P P I S C A E R F i e l d C T O @ P o r t a i n e r . i o j o e p @ t l a - t e c h . i o L i n k e d I N
2. TO BLOATED
3. W H A T D O E S I T M E A N ? ACCUMULATED EXCESS PLATFORM OBESITY 04/31
4. PLATFORM OBESITY 05/31
5. Everyone bought the gym membership Almost nobody puts in the work PLATFORM OBESITY 06/31
6. HOW WE GOT HERE
7. THE CNCF LANDSCAPE IS LIKE A CANDY SHOP
8. WHEN A TOO DEEP HOLE SNOWBALLS OUT OF CONTROL PLATFORM OBESITY 09/31
10. W H A T H A P P E N S N E X T THE CASCADE 1 Cognitive load exceeds capacity. Nobody can hold the whole system in their head. Burnout happens. 2 Operational friction grows. Every change needs a war room. Every upgrade touches everything. 3 Engineering quality degrades. Tests slip. Docs rot. Runbooks go stale. Quietly. 4 Business value evaporates. The business case stops being true. PLATFORM OBESITY 11/31
11. P L U R A L I S T I C I G N O R A N C E EVERYONE IN THE ROOM THINKS THEY'RE THE ONLY ONE STRUGGLING "My platform is messy, bloated and hard to operate. But look at all those conference talks about people running Kubernetes at scale with 150 controllers and zero problems. They must have figured it out. I must be the one doing it wrong." PLATFORM OBESITY 12/31
12. IT'S A CONSTRAINT FAILURE
13. N o n - f u n c t i o n a l r e q u i r e m e n t s PLATFORMS ARE INHERENTLY COMPLEX Scale Hundreds of applications, dozens of multi-cloud environments Governance RBAC, Corporate identity, audit logs, SOC2, PCI, ISO compliance Security Zero-trust, supply chain, runtime, IAM, secrets, BYO HSM, certificate management PLATFORM OBESITY 14/31
14. “Kubernetes is only one piece of the technology puzzle”
15. COMPLEXITY IS THE JOB BLOAT IS A CHOICE BECOME THE PERSONAL TRAINER THAT HELPS THE PLATFORM BECOME FIT AGAIN PLATFORM OBESITY 16/31
16. SAY NO. A LOT
17. FIGHT THE NARRATIVE
18. W H O S E I N T E R E S T , E X A C T L Y ? WHAT IS GOOD FOR THE VENDOR IS NOT NECESSARILY GOOD FOR YOU V E N D O R ' S J O B Sell you their project, product or platform More caloric intake than is healthy for you Y O U R J O B Create a healthy platform within your constraints Everything you need. Nothing you don’t. PLATFORM OBESITY 19/31
19. DESIGN FOR PLATFORM ENGINEERING YOUR CONSTRAINTS
20. STOP COSPLAYING AS A SERVICE PROVIDER
21. THINK SMALL
23. S H A P E O F A T E A M T H A T W I N S SMALL. T-SHAPED. MULTI-DISCIPLINARY. In a team of 20, everyone owns something. When everyone owns something, 20 do the work of 100. 20 DO THE WORK OF 100 PLATFORM OBESITY 24/31
24. SUBTRACTION IS A FIRST-CLASS ENGINEERING SKILL 25/31 PLATFORM OBESITY
25. PLATFORM OBESITY 26/31 BE COMPASSIONATE
26. ABOLISH CEREMONY 27/31 PLATFORM OBESITY
27. BE UNDERWHELMING PLATFORM OBESITY 28/31 1 Can a new engineer understand this quickly? 2 Can we make changes easily? 3 Does it solve a business need? 4 Is there a simpler alternative that is 80% as good?
28. TAKE- AWAYS.
29. PUT IN THE WORK AT THE GYM. 01 Resist the CNCF Candy Shop What is good for the vendor, often isn't good for you 02 Name your constraints. List the five biggest constraints. Work towards fitting your platform to them every day 03 Treat Subtraction as a first-class engineering skills Subtract more than you add, but be compassionate. Consolidate tools. Say 'no' a lot. Reduce unneeded ceremony 04 Be like Mr. T Become a T-shaped expert. Sustainable is harder than impressive. Promote, hire, and praise for seeming underwhelming 05 Think Small Everyone owns something. Stay close to the business, don't isolate yourself. Be a race boat, not a container ship. Don't cosplay as a service provider PLATFORM OBESITY 30/31 06 Don't fall for the pluralistic ignorance Talk to peers about what works and what doesn't. Be honest about your own platform. Don't fall into the trap of 'Platform Engineering'
30. TO SUBTRACT. Less is not a compromise. It's an engineering goal. JP Joep Piscaer, joep@tla-tech.io