6 ms·
> What people really want is not Managed Kubernetes but "namespace as a service". They just want to kubectl apply something and let a background task provision
by sciurus 6y ago
> What people really want is not Managed Kubernetes but "namespace as a service". They just want to kubectl apply something and let a background task provision their machines. They don't want to screw around with RBAC, service meshes, managing the Linux distribution on their worker nodes, managing the master nodes, etc. That service unfortunately doesn't exist.
I think you just described AWS Fargate and Google Cloud Run.
https://aws.amazon.com/fargate/ https://aws.amazon.com/fargate/
https://cloud.google.com/run https://cloud.google.com/run
- jrockway 6y agoAWS's version is pretty half-baked. You can't provision or use persistent volumes (so no stateful apps), and you have to use their load balancer which terminates TLS (preventing your software from being able to do ALPN, using Let's Encrypt, supporting HTTP/3, etc.). Cloud Run just seems like standard "serverless" stuff, nothing to do with Kubernetes. (The downsides involve not being able to run applications that are designed to run on a generic Linux box; everything has to be specially developed. That is fine, and they have open-sourced all the tools necessary to move off of them so you aren't locked in, but it's a bigger paradigm shift.)
- mauflows 6y agoCloud Run uses KNative which is a stateless extension of k8s
- thomasrognon 6y agoI use Cloud Run and nothing is specially developed for it, other than just being stateless. I can take my container and run it on a generic Linux box with zero changes (in fact, I run it in WSL2 on my Windows machine all the time). And I just install the normal Node.js, imagemagick, etc in my Dockerfile, no special builds or flags.
- jrockway 6y agoThat sounds pretty compelling then.