Hi Jason,Thank you for the feedback.
Yes, I believe that's very true and would generally be the case with production deployments. Let me add a note to the slide to include this as well.
I read up on the direct container networking initiative and it's quite interesting to see overlays in action in this context. :-)
ThanksMoiz

From: jsherron(a)pivotal.io
Date: Tue, 23 Aug 2016 18:31:58 +0000
To: cf-dev(a)lists.cloudfoundry.org
Subject: [cf-dev] Re: CF Routing Use Cases

Hi Moiz,
Looks good overall.
My only minor clarification is that the HAProxy configuration that you've shown is only one way to set up CF, and not necessarily what people use in production. For example, on slide 8, the outbound NAT function might be an AWS NAT instance or service separate from HAProxy. [1] The flow you've drawn is still correct, it just might traverse a discrete component. (And more generally, load balancing is often delegated up to a hardware component like an F5 appliance.)
Beyond GoRouter, we're working on an OSS project to enable direct container networking. [2] Deepa Kalani from Plumgrid worked with on it for a period, too.
1 - https://docs.cloudfoundry.org/concepts/security.html2 - https://www.cloudfoundry.org/vision-future-container-networking-cloud-foundry/