Paving the Road to Eirini
summary
Cloud Foundry is run on Kubernetes using SUSE Cloud Application Platform with Eirini so apps become native pods instead of Diego-managed VMs; a 30+ node CF footprint shrinks to about 11 nodes. Integrations include NetApp Trident for automated block volumes, F5 load‑balancer SDN, centralized ELK logging, and backups via Velero plus cf-plugin-backup and physical NetApp snapshots. Networking currently uses flannel and forces multiple CF stacks for isolation; Prometheus is deployed in duplicate for HA. Most features work but require automation and bespoke workarounds before full production parity.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:56Background
- 6:03Main Parts
- 11:29Challenges
- 12:34Storage
- 13:19Backups
- 14:22Platform
- 15:32Logging
- 16:37Monitoring
- 18:10Security
- 20:19Training
- 22:10Future
- 23:23Conclusion
related talks
26mMicroservices With Cloud Foundry and Kubernetes
25m"Kube" your Enthusiasm: Bringing Cloud Foundry and Kubernetes...
28mCloud Foundry 101 for Kubernetes Users
48mKubernetes and or Cloud Foundry - State-of-the-art cloud platforms
31mNew Cloud Foundry Architectures and Features and their Performance Impact
04mSymbiosis Update: The Latest on How SUSE is Bringing...
28mDiego vs Eirini: How to Choose the Best Fitting Container...
46mWhat's Cloud Foundry and why you want to use it