Cloud Foundry Day at KubeCon + CloudNativeCon 2018

Creating a BOSH Cloud Provider Interface (CPI) for Kubernetes (Kube) presents a unique challenge since Kubernetes does not try to hide underlying node updates, unlike a typical IaaS like GCP where VMs are transparently migrated between hosts. While it’s relatively easy to map BOSH concepts to Kube and get a CPI that deploys BOSH releases, BOSH has to behave similarly to the Deployment controller and manage Pod Disruption Budgets (PDBs) in order to automatically maintain expected workload uptime.

In this CPI we have solved these issues by taking advantage of existing Kubernetes primitives and connecting them to existing BOSH workflows. Additionally, as we tested the CPI we have also identified places where we can improve aspects of BOSH – e.g., speed and parallelism of resurrection – which as a whole will improve the BOSH toolset on any platform.

In this talk we will present our working prototype and demo using it to deploy the latest CloudFoundry Application Runtime as well as other releases on Kube. We will also demo updating Kube itself (draining nodes) while keeping BOSH managed workloads running. Secondly, we will discuss preliminary results using the CPI on public Kube offerings such as IBM Cloud, GCP, Azure. Finally, we will briefly mention our upcoming development roadmap.