Re: Announcing support for TCP Routing

Onsi Fakhouri <ofakhouri@...>

Well done y'all! Huge milestone for CF and the routing team!


On Tue, May 10, 2016 at 7:53 PM, Benjamin Black <bblack(a)> wrote:

Great work, everyone!
On May 10, 2016 18:29, "Shannon Coen" <scoen(a)> wrote:

On behalf of the CF Routing team I invite you to bring your non-http
workloads to Cloud Foundry.

By deploying the Routing Release [1] alongside Cloud Foundry and the
Diego runtime backend, operators can enable developers to create TCP routes
based on reservable ports.

The developer UX for pushing an app and mapping a TCP route is as simple
as this:

cf p myapp -d --random-route

The response includes a port associated with the TCP route. Client
requests to these ports will be routed to applications running on CF
through a layer-4 protocol-agnostic routing tier.

The Routing Release is still very much a work in progress. We are
focusing on mitigating stale routing information in the event of network
partition with system components, and on streamlining the deployment

Please review our README for deployment instructions, give it a go. We
are looking forward to your feedback.

Thank you!


- UDP protocols are not supported.
- Both HTTP and TCP routes will be directed to the same application port,
identified by environment variable $PORT. Support for multiple application
ports is coming soon.

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.

Join to automatically receive all group messages.