4 ms·
"Every sufficiently large K8s deployment contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of a PaaS" K8s may well be the best
by ukoki 8y ago
"Every sufficiently large K8s deployment contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of a PaaS"
K8s may well be the best foundation upon which to build a PaaS, but I think building a PaaS should be met with the same eye-rolls as writing your own crypto. Use Heroku or GAE or Elastic Beanstalk or IBM BlueMix or Azure PaaS or Cloud Foundry or Openshift.
- manigandham 8y agoIt's just YAML files, there's nothing to build.
- jacques_chester 8y agoYou can go entirely with YAML in a PaaS. Unless you feel you want it. Just push code. That's it. That's all you need to do.
- manigandham 8y agoHow is that different though? You have to setup the PaaS the first time, the same as you write the YAML file the first time. After that you push code regardless of destination.
- jacques_chester 8y agoI think we have different ideas of what a PaaS is.
- ukoki 8y agoIt's just YAML until you need: * multi-tenancy * auto-scaling * security auditing * automated os/container patching * multi-tenant self-service route/ingress management * multi-tenant self-service logging, monitoring and alerting * multi-tenant self-service databases and so on