- All routing components have been upgraded to golang1.6 details
- Note: GoRouter does not currently support proxying HTTP/2 connections. Requests to backends will be made with HTTP/1.1 details
- New manifest property
suspend_pruning_if_NATS_unavailablecan now be used to suspend pruning of HTTP routes if Gorouter cannot connect to NATS details
Bug Fixes
- Pruning of root route in the presence of a route with a context path previously resulted in an unexpected 502 details
- TCP Emitter attempted to map routes with no external ports details
- Deployment with incorrect manifest configuration for Routing API, TCP Router, and TCP Emitter only failed on Routing API job details
- Deployment did not fail when Routing API cannot save its own route in the database details
Known Issues
- The routing API stores the
router_groupresource in etcd. Router group data is necessary to maintain consistency with the CC API's shared domains, which means that blowing away the data in etcd is not safe when using TCP routing.
Manifest Property Changes
acceptance_tests
| 0.136.0 | 0.137.0 | Default Value |
|---|---|---|
| property did not exist | acceptance_tests.skip_ssl_validation
| false
|
acceptance_tests.cloud_controller.skip_ssl_validation
| Removed property, value is pulled from acceptance_tests.skip_ssl_validation
| |
acceptance_tests.uaa.skip_ssl_validation
| Removed property, value is pulled from acceptance_tests.skip_ssl_validation
|
gorouter
| 0.136.0 | 0.137.0 | Default Value |
|---|---|---|
| property did not exist | router.suspend_pruning_if_nats_unavailable
| false
|
Dependencies
cf-release v239
diego-release 0.1479.0
cf CLI 6.17