CF Networking: All Your Packets Belong to Us - Usha Ramachandran & Angela Chin, Pivotal
summary
Cloud Foundry adds every container has an IP via a CNI-based stack (batteries-included silk CNI replacing flannel) using a VXLAN overlay, with policies stored in a network policy server and enforced by a policy agent that writes iptables rules. CF CLI exposes TCP/UDP app-to-app rules, logging now records denied packets, and the demo shows a visitor app reaching a non-routable homeowner app via Eureka. GA in June and default in PCF 1.11/1.12, and it works end-to-end.
AI-written summary · about
chapters (14)
- 0:00Introduction and team
- 1:28Legacy networking challenges
- 3:16CF networking solution overview
- 5:25Why adopt CNI standard
- 7:17Policy configuration in CF CLI
- 8:45Secure microservices use cases
- 10:09Traffic logging enhancements
- 11:13Control plane architecture
- 15:13Packet flow and policy enforcement
- 17:02Live demo with Eureka
- 19:28Project timeline and milestones
- 22:00Upcoming service discovery features
- 25:39Third-party integrations
- 26:44Resources and Q&A
related talks
32mCF Networking: All Your Packets are Belong to Us
01h 05mCloud Foundry Networking with VMware NSX - Usha Ramachandran, Sai Chaitanya
31mCloud Foundry Networking: Enabling Direct Communication for Microservices - Chin, McClure
29mContainer Networking in Cloud Foundry
01h 03mDeep Dive into Pivotal Cloud Foundry 2.0
06mKeynote: Container to Container Networking for Cloud Foundry and Kubernetes
06mLightning Talk: Cloud Foundry Revisited: UDP, VoIP, and Beyond!
25mEnable IoT and Media Support in CF with Custom TCP/UDP Routers