[jsmthrowaway]

I’m talking about competitors to GKE, which is the entire thesis of that point and that you refuse to acknowledge, which is why you’re knee jerking FUD. I’m a solo developer. I make a Kubernetes app. Do I think Kubernetes is great if I have to build a CloudFormation thing to spin up all of its infrastructure and run it myself, or would I rather pay big company to do it?

The latter.

GKE. EKS/etc. They exist for that use case because that’s where the lock in happens. Now you’re a Kubernetes deployable and too dug in to get off. For a while, your only option was GKE or (God help you, at first) running it yourself. Now other vendors have stepped up to compete, which is the exact situation Google wanted. They shook out the Kubernetes issues with the early adopters with ops experience, then went after pure developers, and had first mover advantage on that customer until the others were forced to respond. I wish I could tell you how many teams I’ve consulted with who when I say “where are we deploying?” immediately say Kubernetes on GKE without a second thought. That is what Google wanted.

This doesn’t take a rocket scientist to figure out, but if you work on Kubernetes I wouldn’t expect you to know this strategy firsthand. It would come from Diane or her people. You’re just having a hootin’ and hollerin’ grand old time building some open source software with a foundation (ooo! So OpenStack!) and mindshare and all the cool kids surrendering their startup to go all in on Kubernetes. Meanwhile, you’re supported by Google, and in fact were conceptualized, to drive sales to Google Cloud. Sorry.

Did you ever ask yourself what the higher level point of Kubernetes is? Like, why throw an entire team on shipping an entire new infrastructure category just to open source it? To make operations better for the industry? Google competes on operations. To use public company capital to chase a hobby? Think about the leadership decision to initiate Kubernetes, and why it was made.

> but you said a whole lot of other crap that is very much misleading in my opinion

The entire comment was quite clearly in support of Google’s decision calculus to not replace Borg. Your rebuttals are honestly more misleading, in my opinion, than my points, because you’re personally wrapped up in it and that’s coming across.

[throwawaykbfud]

>Do I think Kubernetes is great if I have to build a CloudFormation thing to spin up all of its infrastructure and run it myself,

Yes.

>or would I rather pay big company to do it?

Also yes. The two aren't mutually exclusive.

Come on, you've used Borg. You wanna volunteer to going back to just using machines and VMs by hand, or worse, wiring up a complex and unreadable (Ansible|SaltStack|Chef|Puppet) playbook to set everything up?

No. This is why in the early days I was indeed running Kubernetes on AWS, by hand. As the tooling improved it only got better. I honestly wanted to have alternative choices, but Docker continually missed the point with Swarm and I just gave up on it.

>Your rebuttals are honestly more misleading, in my opinion, than my points, because you’re personally wrapped up in it and that’s coming across.

You are projecting wildly on this one.