Global Scale - Geo-Distributed Ingress
Talkat Cloud Foundry Day North America 2024 · on Wednesday, 2024-05-15· at 13:15· Education Center, 2nd Floor·
summary
Comcast operates Cloud Foundry across nine time zones and builds a Global Ingress layer that combines GSLB, an Istio-based global mesh, and edge proxies. Automated provisioning via the Service Broker API cuts network ticketing from weeks to 15 minutes from code to production. For Cloud Foundry the system uses NATS-fed discovery feeders that push routing events to the global ingress, enabling immediate failover, eliminating DNS health-check delays and removing micro‑outages; prototypes work and broader production rollout is ongoing.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 3:36Legacy load balancer challenges
- 5:49Automated service provisioning
- 9:06Limitations of DNS-based routing
- 10:35Introducing Global Ingress
- 13:27Developer experience with Kubernetes
- 15:16Global Ingress for Cloud Foundry
- 18:53Q&A session
- 19:57Summary and future improvements
related talks
24mExpand Cloud Foundry for the Enterprise - Tim Leong, Comcast
47mComcast Cloud Foundry Journey
40mThe Rocket Science of Deploying Cloud Foundry in Multi-Cloud Environments
30mLiberate Your Cloud Foundry Installation From Being Constrained to a Single Cloud
08mIntroduction to the Cloud Foundry at Scale Track - Julian Fischer, anynines & Matthias Steiner, SAP
03mCloud Foundry
29mSetting up a Multi-Cloud, Enterprise-Grade Cloud Foundry Installation: Bridging Infrastructure
30mCloud Foundry: The Gaps