Container Networking in Cloud Foundry
summary
Project delivers layer‑3 container-to-container IPs with a single in‑container interface, plumbed via a CNI plugin adapter and the netman release; batteries‑included proof uses a flannel overlay (VXLAN) that encapsulates packets and tags them with an application identity for policy enforcement. Policy prototypes support same‑space default allow or explicit app‑to‑app allow rules stored in a central “brain.” Code runs today for basic connectivity but does not yet meet all scalability, discovery, or multi‑datacenter goals.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:22Why use containers
- 1:40Project goals
- 5:08Agenda
- 6:23Garden Runcie
- 7:38Address Management
- 9:22Policy
- 13:43Storage
- 14:06Explicit rules
- 15:17Selfservice
- 16:02Cloud Controller
- 16:24Summary
- 17:06Policy Enforcement
- 18:38Details
- 21:01NetMan Drives
- 21:31Discovery
- 23:05Call for Action
- 23:54Office Hours
related talks
32mCF Networking: All Your Packets are Belong to Us
30mCF Networking: All Your Packets Belong to Us - Usha Ramachandran & Angela Chin, Pivotal
31mCloud Foundry Networking: Enabling Direct Communication for Microservices - Chin, McClure
01h 05mCloud Foundry Networking with VMware NSX - Usha Ramachandran, Sai Chaitanya
22mEmbracing OCI and CNI Open Container Standards Between Garden & Friends
43mPanel Discussion: Containers and Networking: A Symbiotic Relationship
27mKeynote: Container Networking
45mMicroservices and containers networking