Kubo - Your Gateway Drug to Cloud-Native - Cornelia Davis, Pivotal
summary
Kubo (commercialized as PKS) runs legacy apps in containers without major refactoring, delivering BOSH-managed Kubernetes clusters that add health management, logging, multi-cloud portability, rolling kernel and k8s upgrades, and higher host density. Enterprises must build approved container images, image-scanning and IAM pipelines for frequently changing apps, and provide smoke tests for rolling upgrades so platform teams can update underneath apps. Experiments show traditional systems like Oracle WebLogic run using statefulsets for stable identities inside Kubernetes.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker background
- 3:14Cloud-native vs traditional workloads
- 7:30Workload categories and 2x2 framework
- 13:12Traditional workloads in containers
- 19:32Kubernetes upgrades and operational benefits
- 22:44Frequently changing traditional workloads
- 25:37Third-party software in Kubernetes
- 30:15Running Oracle WebLogic on Kubo
- 34:29Call to action and Q&A
related talks
01h 12mPKS: The What and How of Enterprise-Grade Kubernetes
34mUsing Kubo to Manage your Kubernetes Clusters [I]
30mDeploying Kubernetes with Cloud Foundry and BOSH
26mA Smooth Path to Cloud Foundry on Containers
01h 02mCloudFoundry or Kubernetes/Kubo: Choosing the Right Platform for the Job
31mStrategies to "Kubernetify" Legacy Applications
34mTaking Back Control: Building Cloud-Agnostic Container Platforms for Regulated Environments
34mKubeflow: Multi-Tenant, Self-Serve, Accelerated Platform for Practitioners