Cloud Foundry Container Runtime is the result of work that Google and Pivotal did over Kubernetes and BOSH.
Kubo aka ‘Kubernetes on BOSH’ is an open source project created jointly by Google and Pivotal.
Why do we need Kubo?
During their talk at the Cloud Foundry Summit (Silicon Valley), Google engineers, Jeff Johnson and Meaghan Kjelland explained that Kubernetes does an excellent job at managing containers and clusters of containers. Whereas BOSH, which is inspired by Google’s Borg system, does an excellent job at managing virtual machines.
However, if you want to use Kubernetes with Cloud Foundry it has many limitations. To overcome those limitations, the engineers from the two companies worked together to bring distant cousins Kubernetes and BOSH closer to each other. The result was Kubo project.
Now, someone needs to maintain and further develop the project. What’s a better home than Cloud Foundry itself. The project was accepted into Cloud Foundry incubation and considering how critical it is for the Cloud Foundry community, it has been renamed as Cloud Foundry Container Runtime (CFCR).
CFCR is yet another great example of open collaboration in the open source world. It brings the best of both worlds. You get Google, that created Kubernetes and Pivotal that ‘created’ Cloud Foundry and BOSH, to work on the same solution. Personally, I like the name Kubo; Cloud Foundry has some cool names for their other projects, so why CFCR?
Back to the main point. Cloud Foundry has launched CFCR as the default container deployment method for Cloud Foundry using Kubernetes and BOSH.
Cloud Foundry users can now use Container Runtime to deploy Kubernetes or Application Runtime (previously Elastic Runtime) for a Cloud Application Platform. In either case, BOSH underpins infrastructure provisioning for both Cloud Foundry runtimes.
“Kudos to the great Cloud Foundry community and the Foundation for being able to rapidly embrace and incorporate Kubernetes with the Kubo project — now Container Runtime — to take this next evolutionary step for Container Orchestration,” said Marco Hochstrasser, Head of Application Cloud, Swisscom. “Swisscom sees great opportunities in working with this technology in the future.”
Cloud Foundry said in a press release that both Cloud Foundry Application Runtime and Container Runtime are built with developers in mind, providing flexibility to run apps in any language or framework on any cloud. This flexibility extends to services as well, thanks to the Open Service Broker API, which makes it easy to integrate the services your apps need to run—on both Application Runtime and Container Runtime.