CF + Kubo: Choosing the Right Platform for the Job
summary
Kubo is presented as a BOSH release that deploys and manages highly available Kubernetes clusters across clouds and is now a Cloud Foundry incubator/container runtime; Pivotal’s PKS adds a registry, NSX-T networking, and an enterprise upgrade/patch cadence. The demo wires Spring Cloud Data Flow on Cloud Foundry to an Elasticsearch cluster on Kubernetes, ingesting thousands of earthquake records (4k→6k in seconds), showing Kubo = BOSH release for Kubernetes and demo: Spring Cloud Data Flow → Elasticsearch on K8s working end-to-end.
AI-written summary · about
chapters (18)
- 0:00Introduction and overview
- 1:01Workloads in modern cloud
- 3:53Abstractions in cloud platforms
- 6:43Container vs application platforms
- 10:16Operational challenges
- 13:06Cloud Foundry application runtime
- 14:57Kubernetes as container orchestrator
- 16:40Project Kubo explained
- 17:22Elastic runtime vs container runtime
- 20:14Pivotal Container Service features
- 21:18Cluster provisioning with service broker
- 22:22Enterprise Kubernetes updates
- 23:44Integration points between CF and K8s
- 25:09Demo setup and architecture
- 27:19Deploying Elasticsearch on K8s
- 28:42Spring Cloud Data Flow pipeline
- 30:51Data visualization and results
- 32:36Q&A session
related talks
01h 02mCloudFoundry or Kubernetes/Kubo: Choosing the Right Platform for the Job
30mDeploying Kubernetes with Cloud Foundry and BOSH
34mUsing Kubo to Manage your Kubernetes Clusters [I]
23mCloud Foundry and Kubernetes: A Peanut Butter & Jelly Application
01h 12mPKS: The What and How of Enterprise-Grade Kubernetes
19mPaaS on Kubernetes: Journey of Making Cloud Foundry Kubernetes Native
31mCloud Foundry Container Runtime: BOSH-Powered Kubernetes
38mLet's Run Cloud Foundry on Kubernetes