Diego vs Eirini: How to Choose the Best Fitting Container...
summary
Eirini makes the Cloud Foundry scheduler swappable by translating CF droplets into Kubernetes objects and reusing an existing k8s cluster; it runs with BOSH-produced droplets, Garden containers, Helm-deployed CF containerization charts and is alfa-available on IBM Cloud. Diego remains a lightweight, CF-tailored scheduler with stronger Windows support and simpler operator model. Choice depends on skills and use case: Eirini bridges Cloud Foundry and Kubernetes and enables a single orchestrator, while Diego optimizes for CF assumptions and Windows workloads.
AI-written summary · about
chapters (9)
- 0:00Introduction to containerization
- 1:03The role of container orchestrators
- 4:04Introducing Eirini
- 5:50Why Kubernetes?
- 7:31Cloud Foundry vs. Kubernetes
- 9:42Architecture and similarities
- 13:47Diego and Eirini use cases
- 17:50Operational strategies
- 23:05Summary and Q&A
related talks
32mImplementing the Schedulers: A Look at the Internals of Diego...
37mCloud Foundry Diego Overview
25mPaving the Road to Eirini
22m"Cube" your Enthusiasm: Bringing CF and Kubernetes Together with...
35mResource Management Ecosystem and Cloud Foundry - A Review of the State of the Art
32mCloud Foundry Diego Update
28mEirini vs. Knative - A Comparison
48mKubernetes and or Cloud Foundry - State-of-the-art cloud platforms