3 ms·

I just thought of another reason. Rolling your own cluster forces you to understand what Kubernetes is at a basic level. If you never get that experience, and j

I just thought of another reason. Rolling your own cluster forces you to understand what Kubernetes is at a basic level. If you never get that experience, and just roll with cloud services, you aren't really getting that and will tend to get mystified by errors which, you'd have a much better idea of where they're at if you've rolled your own. Kubernetes is very complicated, but the complexity can be managed if you approach it from the bottom up. Using a cloud service robs you of that ability.

emodendroket 6y ago
The pitch for Kubernetes is kind of supposed to be “infrastructure as a service,” isn’t it?
- vinceguidry 6y ago
  No, that's the pitch that Amazon / Google makes. Kubernetes has a much more complicated value proposition that you have to grasp the hiring dynamics of Google to really understand. Google hires really smart people but smarts isn't necessarily skills. So it builds tech to leverage that workforce. Other companies hire skilled people that aren't necessarily super-smart, because super-smart people can make a lot more money at Google. So other companies use Google / Amazon, they don't really care what underlying techs it uses, so long as they know they'll be able to hire people with the skills. If you're rolling your own Kubernetes, you're putting your faith in your own smarts, because you're largely on your own. K8s rewards a certain kind of developer, and badly punishes someone thinking running their own k8s is going to be as seamless a process as consuming GCP resources.
  - emodendroket 6y ago
    Yeah but that’s my point, not everyone needs to actually set it up. The intent is for most to just be users and concern themselves with editing yml files to bring up their services.
Shared404 6y ago
> Kubernetes is very complicated, but the complexity can be managed if you approach it from the bottom up. s/Kubernetes/Computers

emodendroket 6y ago

The pitch for Kubernetes is kind of supposed to be “infrastructure as a service,” isn’t it?

vinceguidry 6y ago
No, that's the pitch that Amazon / Google makes. Kubernetes has a much more complicated value proposition that you have to grasp the hiring dynamics of Google to really understand. Google hires really smart people but smarts isn't necessarily skills. So it builds tech to leverage that workforce. Other companies hire skilled people that aren't necessarily super-smart, because super-smart people can make a lot more money at Google. So other companies use Google / Amazon, they don't really care what underlying techs it uses, so long as they know they'll be able to hire people with the skills. If you're rolling your own Kubernetes, you're putting your faith in your own smarts, because you're largely on your own. K8s rewards a certain kind of developer, and badly punishes someone thinking running their own k8s is going to be as seamless a process as consuming GCP resources.
- emodendroket 6y ago
  Yeah but that’s my point, not everyone needs to actually set it up. The intent is for most to just be users and concern themselves with editing yml files to bring up their services.

Shared404 6y ago

> Kubernetes is very complicated, but the complexity can be managed if you approach it from the bottom up. s/Kubernetes/Computers