I wonder if finding anything related to Kubernetes sidecars, cluster configuration, or tools boring or unnecessary is a career limiting move.
Update: After spending a bit more time thinking about this, I’m wondering if the reasons why things like this get so complicated is a mixture of:
- Larger teams getting split into smaller ones, and needing a way for them to work more or less independently without stepping on each other’s toes,
- Leaning towards the security side on the security vs. convenience (or rather simplicity) continuum,
- Saying “It’s what Google/Amazon/Spotify/whoever does” without taking into account that they’re got 100x more developers and 10,000,000x more users than we do.
And this complexity tends to cascade onto itself: throwing one more tool in means that we need to secure it, which means more configuration, which means that we need a tool to manage that, which adds more security, and on and on it goes.
This is not helped by people always looking out for the new and shiny. It might be because I’m getting old and cynical but that appeal is wearing off on me.
And yeah, people could make the argument for why we need each one of these. It’s the classic “the road to hell is paved with good intentions” situation here.
✍️ Reply by email