Why Do I Need Kubernetes When I Already Have Cloud Foundry? - Sanjay Patil, SAP
summary
SAP explains why Cloud Foundry stays for fast developer experience while Kubernetes handles stateful, hardware‑bound and multi‑node topology needs; concrete use cases include ACP Data Hub (data pipelines run close to sources), blockchain and machine‑learning on GPUs, and SCP Concur where over 30 services in SCP Concur are being containerized. They built and open‑sourced Gardener seed/garden/shoot model to provide a multi‑cloud cluster‑as‑a‑service that creates clusters in minutes, uses Kubernetes to manage control planes, supports AWS/Azure/GCP/OpenStack/Ali and exposes RBAC.
AI-written summary · about
chapters (8)
- 0:00Introduction and agenda
- 2:55Cloud Foundry overview
- 7:03Why Kubernetes is needed
- 11:26Kubernetes use cases at SAP
- 17:17Project Gardener
- 22:11Gardener live demonstration
- 28:28Integration and vision
- 33:40Q&A session
related talks
15mThe Cloud Foundry Renaissance
36mMulti-Cloud with Cloud Foundry: Making It Real - Dmitry Bakaleinik, SAP & Sean McKenna, Microsoft
01h 02mCloudFoundry or Kubernetes/Kubo: Choosing the Right Platform for the Job
39mYou Don’t Need Kubernetes to Be Cloud Native
08mRun Cloud Foundry at Scale
48mKubernetes and or Cloud Foundry - State-of-the-art cloud platforms
30mPanel: Cloud Foundry and Kubernetes - The Blending Continues
11mConversation with Marc Geall, Senior Vice President, General Manager, SAP Cloud Platform