A few weeks ago, I attended Cloud Foundry summit Europe 2017 held in Basel, Switzerland. One of the more interesting topics that came up was the “Cloud Foundry Container Runtime,” an effort formerly known as “Kubo.”
Kubo, which comes from “Kubernetes on Bosh,” was created jointly by Pivotal and Google in order to provide a simple way to deploy and operate production-ready Kubernetes clusters on-premise and in the cloud. Back in June, the Kubo code was donated to the Linux Foundation as an open source project.
To learn more about Cloud Foundry Container Runtime (nee Kubo) and the larger context it fits within, I sat down with Ian Andrews, Vice President of Products at Pivotal. Armed with only a pen and paper, Ian provides an overview of the container runtime and explains how it differs from the Cloud Foundry application runtime, as well as which workloads are most appropriate for each.
Ian ends by walking us through the recently announced, Pivotal Container Service (PKS) that VMware and Pivotal worked on together with help from the Google cloud team (PKS is based on the Cloud Foundry container runtime with extra goodies thrown in).
- Take Kubernetes, and bish bash BOSH, you’ve got Container Runtime – The Register
- Cloud Foundry Morphs Kubo into Container Runtime – sdxcentral
- VMware teams up with Pivotal, Google Cloud on new container service – ZDNet
- Google, VMware and Pivotal team for on-premises Kubernetes – The Register
- Choosing the Right Tool for Your App Modernization Project – VMware | Blogs