Release 0.183.0 · cloudfoundry/routing-release

Release Highlights

Operator can specify HTTP headers to be added by Gorouter to responses details
Operator can specify HTTP headers to be removed by Gorouter from responses details
We have updated locket to the latest commit details
Fixed an issue introduced with the move to BPM for TCP Router on accumulating TCP-Router HAProxy instances details
With the move to BPM, operators should colocate syslog-release for access log streaming. enable_access_log_streaming is no longer supported in the Gorouter details
Gorouter stdout logs includes vcap_request_id so operators can correlate the stdout logs with access logs for easier debugging of issues details
Route registrar now supports registration of TCP routes details
When an application instance crashes while processing a request Gorouter now returns an error and takes the backend out of the pool temporarily, without retrying another backend. This change may cause increased 502 rates for existing apps details.
We have updated from Cflinux2 to Cflinuxfs3 details
We are still evaluating the issue we are having with performance reports and have not been able to get a root cause details

0.182.0	0.183.0	Default Value
did not exist	`router.tls_port`	443
did not exist	`router.http_rewrite.responses.add_headers_if_not_present`
did not exist	`router.http_rewrite.responses.remove_headers`
`router.enable_access_log_streaming`	no longer supported
did not exist	`route_registrar.routing_api.api_url`	`http://routing-api.service.cf.internal:3000`
did not exist	`route_registrar.routing_api.oauth_url`	https://uaa.service.cf.internal:8443
did not exist	`route_registrar.routing_api.client_id`	`routing_api_client`
did not exist	`route_registrar.routing_api.client_secret`
did not exist	`route_registrar.routing_api.ca_certs`
did not exist	`route_registrar.routing_api.skip_ssl_validation`	`false`
did not exist	`route_registrar.routes` now supports `type`, `router_group`, and `external_port`