cloudfoundry/routing-release 0.138.0 on GitHub

Gorouter can now be optionally configured to send Zipkin tracing HTTP headers X-B3-TraceId and X-B3-SpanId; these are also logged in the access log details
Gorouter now logs the NATS IP and port it connects to details
Gorouter now supports a configurable delay after which a newly started router begins listening for requests before bosh considers the process up details
Gorouter now logs unregister and pruning messages at an Info log level details
Gorouter now logs app index in access log details
The HTTP User-Agent header for which Gorouter responds to healthchecks from load balancers is now configurable details
Gorouter route pruning can optionally be suspended when NATS is unavailable details
Gorouter now healthchecks NATS every 20 seconds so in the event of a NATS failure it will failover to a health NATS node and still have enough time to receive route registrations before pruning routes details
Route-registrar now healthchecks NATS every 20 seconds details
In Progress: Routing API support for MySQL/PostgreSQL details
- In order to support a relational database, and still support event streams, Routing API instances now run in active/standby configuration, using Consul for lock details

Bug Fixes

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.

0.137.0	0.138.0	Default Value
property did not exist	`router.tracing.enable_zipkin`	false
property did not exist	`router.load_balancer_healthy_threshold`	20
property did not exist	`router.healthcheck_user_agent`	HTTP-Monitor/1.1
property did not exist	`router.suspend_pruning_if_nats_unavailable`	false