This repository is a BOSH release for deploying Gorouter, TCP Routing, and other associated tasks that provide HTTP and TCP routing in Cloud Foundry foundations.
Our BOSH release is available on bosh.io and on our GitHub Releases page.
If you have a concrete issue to report or a change to request, please create a Github issue on routing-release.
Issues with any related submodules (Gorouter, Routing API, Route Registrar, CF TCP Router) should be created here instead.
You can also reach us on Slack at
cloudfoundry.slack.com in the
#cf-for-vms-networking.
channel.
See the Contributing.md for more information on how to contribute.
The TCP Router and Routing API are stateless and horizontally scalable. The TCP Routers must be fronted by a load balancer for high-availability. The Routing API depends on a database, that can be clustered for high-availability. For high availability, deploy multiple instances of each job, distributed across regions of your infrastructure.
For details refer to Routing API.
For documentation on metrics available for streaming from Routing components through the Loggregator Firehose, visit the CloudFoundry Documentation. You can use the NOAA Firehose sample app to quickly consume metrics from the Firehose.
For more information on how Routing release accomplishes session affinity, i.e. sticky sessions, refer to the Session Affinity document.
X-CF Headers describes the X-CF headers that are set on requests and responses inside of CF.
