Eirini vs. Knative - A Comparison
summary
Eirini implements Cloud Foundry on Kubernetes, preserving cf push and buildpack workflows via an OPI (Orchestration Provider Interface) so enterprises get a migration path; it behaves like a platform. Knative is a set of building blocks: Knative build deprecated/removed in 0.7–0.8 so Tekton or external pipelines are needed, serving supports autoscale and scale-to-zero but observed cold starts around 30s, and eventing offers CloudEvents, channels and protocol bridging rather than a full CF-style solution.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker intro
- 3:14Eirini vs Knative overview
- 9:21Eirini’s Cloud Foundry heritage
- 13:57Knative’s building block nature
- 18:10Knative eventing and serving
- 22:50KF project and user experience
- 27:54Q&A and closing remarks
related talks
40mKnative vs Cloud Foundry: Where are the Overlaps...
25m"Kube" your Enthusiasm: Bringing Cloud Foundry and Kubernetes...
26mMicroservices With Cloud Foundry and Kubernetes
48mKubernetes and or Cloud Foundry - State-of-the-art cloud platforms
28mDiego vs Eirini: How to Choose the Best Fitting Container...
55mServerless On Your Own Terms using Knative
31mKnative: Is it for me?
20mKnative: A Kubernetes Framework to manage Serverless Workloads
