CloudFoundry or Kubernetes/Kubo: Choosing the Right Platform for the Job
summary
Compares Cloud Foundry + BOSH vs Kubernetes on BOSH with concrete demos: Spring Cloud Data Flow apps run on Cloud Foundry while Elasticsearch runs in a Kubo cluster on GCP, streaming thousands of earthquake records per second into Kibana. Shows BOSH repaves VMs with zero downtime (customer repaves 2,000 app instances in <5 hours), installation times (~3h for CF, ~2–3h to provision Kubo), and CF create-service provisions Kubo clusters via a service broker.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 6:50Flexibility
- 7:35Different perspectives
- 8:59Operational challenges
- 13:54Cloud Foundry
- 16:59Kubernetes
- 20:29Health Monitoring
- 21:09Kubernetes Mindset
- 22:42Kubernetes is not easy to operate
- 24:13Project Kubo
- 29:57Project Pivotal
- 36:40Compatibility
- 38:00Choosing the right workload
- 42:45Elastic Search Dashboard
- 43:20Data Flow Server
- 43:56Data Flow Integration
- 45:34Data Flows Purpose
- 47:12Elastic Search Sync
- 48:49Cloud Foundry Command Line
- 50:22RabbitMQ
- 51:24Demo
- 52:47Questions
related talks
39mCF + Kubo: Choosing the Right Platform for the Job
30mDeploying Kubernetes with Cloud Foundry and BOSH
06mLightning Talk: Kubo: A Tale of Three Products
48mKubernetes and or Cloud Foundry - State-of-the-art cloud platforms
31mCloud Foundry Container Runtime: BOSH-Powered Kubernetes
28mCloud Foundry 101 for Kubernetes Users
19mPaaS on Kubernetes: Journey of Making Cloud Foundry Kubernetes Native
48mCloud Foundry - your PaaS on OpenStack