|
|
|
|
|
|
by mijoharas
1 day ago
|
|
|
> That the tech benefits may not be there, but they’re using it for the non-tech benefits My read of the article is that this is correct, but that the benefits they're using it for are the operational, and organisational. I think the comment you're replying to is arguing that those benefits don't really matter or outweigh the additional complexity costs when N=2 (engineers). I think I'd probably agree. |
|
|
If K8s is new to you, sure. Definitely not the time to learn it.
But I can see a world where it’s fine to use early on.
Especially if your team is cloud native. K8s isn’t really a new controversial toy in my eyes, it’s pretty well supported and good enough for most things out of the box.
I just don’t think it’s as big a deal as the “CTO IS WASTING EVERYONES TIME” argument.