Interesting discussion developing on this latest post by Komodor Co-founder and CTO Itiel Shwartz. What's your take on the two key truths Itiel mentioned? Is there more to it than different KPIs and the knowledge gap? Let us know!
Does Kubernetes make DevOps hate developers? (even more than they used to) After 4.5 years of building Komodor and talking to countless DevOps teams, I keep seeing the same pattern; almost every conversation with DevOps teams seems to echo the same frustrations: 1. “Developers simply don’t get it.” 2. “We have a culture problem” 3. “They just escalate everything to us.” 4. “Just read the F*cking logs!” With Kubernetes’ dual nature, where infrastructure and application are deeply intertwined, these tensions aren’t just fleeting problems - they’re becoming more entrenched. But here’s the thing - it doesn’t have to be this way. I genuinely believe developers and DevOps can and should be friends (certainly not enemies!). In my experience, most frustrations boil down to two key truths: Different KPIs - When developers are measured solely on shipping features, maintenance and support naturally take a backseat. It’s not about bad intentions; it’s about incentives. Knowledge Gap - DevOps teams live and breathe Kubernetes (80% of their time), while for most developers, it’s more like 5%. This asymmetry creates inevitable friction. Once ops and platform teams accept these truths, finding the right tools and processes to support one another becomes much simpler… If someone else has a different perspective or experience, I would be happy to hear how it works in your org :) #kubernetes #devops #developers #tech