3 ms·
That mindset - being able to build all types of application on top of the "platform" - is why OpenShift rehosted itself on top of Kubernetes. Being able to com
by smarterclayton 10y ago
That mindset - being able to build all types of application on top of the "platform" - is why OpenShift rehosted itself on top of Kubernetes. Being able to compose building blocks and run higher level services (batch, application, clustered pets, 12-factor, legacy, etc) means you're much closer to the Goldilocks zone of Datacenter infra. I.e. avoiding needing to deploy multiple application stack platforms.
Disclaimer - I work on OpenShift and Kubernetes
- jacques_chester 10y agoWe saw the same gaps with Cloud Foundry -- the CF v2 API is resolutely about apps, the whole app and nothing but the app. That's one of the reasons that the Diego effort was launched and it's why the v3 API is under development. Red Hat has rebased on Kubernetes, but at the time we launched Diego, there was no alternative to building it ourselves. I note that the workloads you mentioned are all supported or supportable by Diego and we're building out the missing ones very rapidly. Disclaimer: I work for Pivotal, we donate the majority of engineering on Cloud Foundry. I am not near the Diego or core runtime teams, so my version of events may be hilariously inaccurate.