Services on Container Runtime (or, ""You mean I don't have to write a BOSH release?"") Our team, Pivotal Cloud Foundry Platform Engineering, works with software vendors to integrate their service software with Cloud Foundry. Using lessons we've learned from years of this integration work, we give a sneak peek of how Container Runtime can improve this experience for software vendors, application developers, and operators. = Motivation = Want your service software to Cloud Foundry? Build a BOSH release. BOSH does great things, but: - BOSH is hard (at least has a steep learning curve) = high cost. - BOSH is not widely used outside of Cloud Foundry = low reward. = Opportunity = Container Runtime provides a new deployment mechanism. Kubernetes deployments are: - Less difficult = less expensive. - Widely used = higher reward, and might already be done. = Approach = We will explain how: - Software vendors can use existing Kubernetes deployments on Container Runtime. - We are developing a generic Service Broker for on-demand Kubernetes service deployments, saving software vendors the hassle. - Application developers keep the familiar `cf create-service` and `cf bind-service` interface. - Operators can easily deploy these services. Speaker: Mikey Boldt, Pivotal Recorded At SpringOne Platform 2017.
Go to the next level at SpringOne Platform. Save $200 by July 31st.Register Now