Why Do I Need Kubernetes When I Already Have Cloud Foundry? - Sanjay Patil, SAP

Why Do I Need Kubernetes When I Already Have Cloud Foundry? - Sanjay Patil, SAP
Like many of you, several SAP teams have also been asking this question to themselves. While the answer is singular in some cases (either Cloud Foundry or Kubernetes), in many situations, there is room or rather a need for both these technologies. In this session, you will learn why several SAP teams have adopted Kubernetes / container model for developing comprehensive solutions (more than what a typical ‘cf push’ can handle) and deploying them on-premise and/or in the cloud. Some of these Kubernetes based solutions are also exposed as services in Cloud Foundry environment, whereby Cloud Foundry applications can consume them via the simple and familiar service binding paradigm.
About Sanjay Patil
Sanjay Patil is a Product Manager of SAP Cloud Platform, a certified Cloud Foundry PaaS solution. With his passion and decade-long experience with Open Standard technologies, Sanjay has been closely involved in creation and launch of the Cloud Foundry Foundation. He has delivered talks on Cloud Foundry topics at previous Cloud Foundry Summits as well as other conferences such as SAP TechEd.

[@balajimathu]

Very clear simple and detailed explanations. Thanks Sanjay. I like the way he make jokes to keep things simple

[@yehudawatson8674]

Instablaster.

[@hackebeil20]

clear talk. thank you!

[@AnthonyMcCulley]

Good talk. Couple of comments. "Greater freedom and control over infrastructure bindings, network designs" Depending on the level of granularity you need, this can also be achieved via isolation segments in CF. The overhead of doing so is probably not worth it if you are talking about segmenting by team or product, but if you want to segment by a particular multi-team function or aggregation of closely-related applications, it would work just fine. Also, 1 of the key reasons for using Kubernetes alongside CF is for vendored applications that come pre-packaged/configured as a container. Most off-the-shelf solutions we buy and use won't come packaged as code, buildpack, and instructions for setting up a database.