5 ms·

Businesses may not specifically want "decentralization idealism", that's true. What they want is "Windows for Web". Something where you could install an app an

Businesses may not specifically want "decentralization idealism", that's true. What they want is "Windows for Web". Something where you could install an app and bingo, it instantly worked on all endpoints around the globe. Or where you once install "yet another CDN provider" component (app), and it instantly and automatically covers all the installed apps. Kubernetes came close to this, but it requires significant amount of expertise, and honestly it is a matter of time until it gets smashed with something better. In short, what we (businesses) want is "Click and serve". Sandstorm was so close and yet did not make the expected steps in that direction. This makes me sad, but this is life.

sascha_sl 7y ago
>Kubernetes came close to this, but it requires significant amount of expertise, and honestly it is a matter of time until it gets smashed with something better. I wish this was true, because a lot of code in Kubernetes is garbage and their entire architecture of constant reconciliation is quite wasteful, but at this point is has essentially won in being supported by vendors. It'll be a long time before something can really push it away. Which sucks, because nobody wants (operational complexity) or can run it outside an enterprise environment, at least not in a way where you can expect a majority of helm charts to work (insanely high compute requirrements for control/instrumentation plane, requirement for loadbalancer and PVC provisioner implementation) I really want a unified "let's not think about servers" model for using compute and storage but kubernetes is not it for consumers.
- mwcampbell 7y ago
  Over-complicated "industry standard" solutions tend to fade away after the hype has died down. Examples that come to mind include SOAP and OpenStack. If you think Kubernetes falls into that category, I think it will go the same way before too long.
  - sascha_sl 7y ago
    The difference between OpenStack and Kubernetes is that one was meant to power alternative private clouds and the other just adds an abstraction layer on top of public clouds so everyone can buy into the lie of being independent from them. In my experience the bare metal code paths in Kubernetes are anywhere from mostly untested over entirely broken to just not supported in the first place.
    - kissgyorgy 7y ago
      It's clear that you have zero experience with Kubernetes on bare metal. Why bother commenting on the topic then?
    - dankohn1 7y ago
      Here are 26 private cloud Kubernetes users who would disagree: https://www.cncf.io/projects/case-studies/?_sft_cloud_type=private https://www.cncf.io/projects/case-studies/?_sft_cloud_type=p...
      - deleted 7y ago
        [deleted]

sascha_sl 7y ago

>Kubernetes came close to this, but it requires significant amount of expertise, and honestly it is a matter of time until it gets smashed with something better. I wish this was true, because a lot of code in Kubernetes is garbage and their entire architecture of constant reconciliation is quite wasteful, but at this point is has essentially won in being supported by vendors. It'll be a long time before something can really push it away. Which sucks, because nobody wants (operational complexity) or can run it outside an enterprise environment, at least not in a way where you can expect a majority of helm charts to work (insanely high compute requirrements for control/instrumentation plane, requirement for loadbalancer and PVC provisioner implementation) I really want a unified "let's not think about servers" model for using compute and storage but kubernetes is not it for consumers.

mwcampbell 7y ago
Over-complicated "industry standard" solutions tend to fade away after the hype has died down. Examples that come to mind include SOAP and OpenStack. If you think Kubernetes falls into that category, I think it will go the same way before too long.
- sascha_sl 7y ago
  The difference between OpenStack and Kubernetes is that one was meant to power alternative private clouds and the other just adds an abstraction layer on top of public clouds so everyone can buy into the lie of being independent from them. In my experience the bare metal code paths in Kubernetes are anywhere from mostly untested over entirely broken to just not supported in the first place.
  - kissgyorgy 7y ago
    It's clear that you have zero experience with Kubernetes on bare metal. Why bother commenting on the topic then?
  - dankohn1 7y ago
    Here are 26 private cloud Kubernetes users who would disagree: https://www.cncf.io/projects/case-studies/?_sft_cloud_type=private https://www.cncf.io/projects/case-studies/?_sft_cloud_type=p...
    - deleted 7y ago
      [deleted]