Something I often hear is that Kubernetes is a tool that enables one to build a PaaS.
When I look at the compute options available, I think rolling your own PaaS on top of Kube is akin to painting yourself into a corner.
It doesn’t come across as very forward thinking.
When I look at the compute options available, I think rolling your own PaaS on top of Kube is akin to painting yourself into a corner.
It doesn’t come across as very forward thinking.
Cloud vendors have the personnel and the resources to easily keep up with the latest and greatest in the OSS world and roll out things like “serverless pods” (by, I suspect, making things like their custom FaaS runtimes OCI compatible) or whatever the next fad is.
Building out an internal platform on top of Kube that will offer the same degree of choice, ease and freedom as available in the public cloud seems pretty quixotic.
It’s going to be incredible difficult for small-ish internal infra teams to keep up.
It’s going to be incredible difficult for small-ish internal infra teams to keep up.
Let me be clear. I’m not saying “it’s public cloud or bust”.
I just think going all in with a “container” based PaaS as the “Kubernetes strategy” is tantamount to willfully restricting yourself from leveraging the most innovative features of the cloud. That’s disappointing.
I just think going all in with a “container” based PaaS as the “Kubernetes strategy” is tantamount to willfully restricting yourself from leveraging the most innovative features of the cloud. That’s disappointing.
Containers did not become popular because it was the best way to run applications for the wider developer community.
Containers became popular because it became the marketing cry for a tool that solved a whole different problem.
Exhibit A 👇
Containers became popular because it became the marketing cry for a tool that solved a whole different problem.
Exhibit A 👇
Even if you painstakingly build a container based PaaS on top of Kube today, in a couple of years it’s going to end up looking outdated compared to what’s possible in the public cloud.
I hope Kube can - and I suspect will - evolve to be able to run more types of workloads.
I hope Kube can - and I suspect will - evolve to be able to run more types of workloads.
Kube might’ve begun it’s life as OSS heavily inspired by an internal Google tool, but that tool was originally designed in the mid 2000s when the compute landscape looked very different.
And no, evolving won’t make Kube the next openstack (anymore than it already is).
And no, evolving won’t make Kube the next openstack (anymore than it already is).
