cloudfoundry/routing-release 0.139.0

on GitHub

• PCRE has been updated in TCP Router to 8.39 details
• Gorouter now offers HTTP healthcheck endpoint /health on port 8080 (configurable via existing router.status.port property) with support for properties router.load_balancer_healthy_threshold and router.drain_wait details
• TCP Router now offers HTTP healthcheck endpoint /health on port 80 (configurable with property haproxy.health_check_port) details
• Gorouter will route a request that contains a valid value for X-Cf-App-Instance HTTP header to the specified backend details
• Gorouter now accurately reports in access log the number of bytes sent in the response body when returning an error details
• Gorouter now supports optionally forcing the value of X-Forwarded-Proto sent to backends to https when an upstream component is terminating TLS but does not support sending HTTP headers

Support for Zipkin tracing

• When Zipkin tracing is enabled, if request does not include both X-B3-TraceId and X-B3-SpanId HTTP headers, router will initiate a new trace id details
• When Zipkin tracing is enabled, and request includes both X-B3-TraceId and X-B3-SpanId, Gorouter will forward HTTP header X-B3-ParentSpanId to the backend, set to the value of X-B3-SpanId in the received request details
• When Gorouter initiates a trace, X-B3-TraceId and X-B3-SpanId headers are set to the same value details

In Progress

• Routing API support for MySQL/PostgreSQL details

Known Issues

• The routing API stores the router_group resource 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

gorouter