Twitter | Search | |
This is the legacy version of twitter.com. We will be shutting it down on 15 December 2020. Please switch to a supported browser or device. You can see a list of supported browsers in our Help Center.
Ben Johnson
My rule of thumb is that you’ll probably spend at least $1M to move to Kubernetes. That’s new ops hires, training, initial productivity loss, etc. If you don’t have a $1M problem that Kubernetes is solving then I don’t think you should even consider it.
Reply Retweet Like More
David McKay Oct 17
Replying to @benbjohnson
That figure isn't that outrageous, but how much of it is current spend scaling systems on the cloud and over provisioning their ceiling in lieu of bin packing, servers for Consul, HAProxy, configuration management cycles, monkey patching and software upgrades. It's not new spend
Reply Retweet Like
Ben Johnson Oct 17
Replying to @rawkode
If you’re already doing all that stuff at scale then $1M is probably not a ton of money. Yeah, it can totally make sense then.
Reply Retweet Like
Alexander Morozov Oct 17
Replying to @benbjohnson
But the real 1M$ will be the friends you'll make complaining about it in the Twitter :)
Reply Retweet Like
Ben Johnson Oct 17
Replying to @LK4D4math
🤞🤞
Reply Retweet Like
A.D. Oct 18
Replying to @benbjohnson
And if you start with it ?
Reply Retweet Like
Ben Johnson Oct 18
Replying to @themoah
Godspeed! 😂
Reply Retweet Like
Aidan W Steele Oct 17
Replying to @benbjohnson
What size org do you think you need to spend $1M? We would have sunk way more into that with ~1K tech staff
Reply Retweet Like
Aidan W Steele Oct 17
Replying to @benbjohnson
I forgot to add, I emphatically agree with the point you’re making. Just think it’s likely understating the magnitude!
Reply Retweet Like
Kyle Cordes (kylecordes.com) Oct 17
Replying to @benbjohnson
This is probably a good rule of thumb, but we have a k8s shaped problem at a much smaller scale in an internal system where we need to orchestrate a bunch of containers for test environments. Surely it's worse to solve this problem without k8s.
Reply Retweet Like
Ben Johnson Oct 17
Replying to @kylecordes
Yeah, I’m sure there’s exceptions to the rule. If you know what you’re in for and you have a Kubernetes-shaped problem then go for it.
Reply Retweet Like