3 ms·
This makes a ton of sense for Cloud Foundry: Let others do the heavy lifting on infrastructure, and go up the stack. Next stop: istio for routing?
by wstrange 8y ago
This makes a ton of sense for Cloud Foundry: Let others do the heavy lifting on infrastructure, and go up the stack.
Next stop: istio for routing?
- jacques_chester 8y agoIstio integrations have been underway for some time now: https://github.com/cloudfoundry/istio-release https://github.com/cloudfoundry/istio-release (and this article by SUSE folks is good too: https://www.suse.com/c/istio-a-new-routing-tier-for-cloud-foundry/ https://www.suse.com/c/istio-a-new-routing-tier-for-cloud-fo...). Something that struck me other day is that Kubernetes is evolving in the opposite direction from Cloud Foundry. In Cloud Foundry the effort to extract Diego from the Cloud Controller and DEAs was an epic quest, but in the end successfully separating the "god controller" from container scheduling. Meanwhile, in Kubernetes, it started with a nice clean container scheduler and now ... now everyone is stuffing everything into the Kubernetes master. I wonder when (or if) Kubernetes's Diego moment will come.