Re: routing-release 0.141.0

Mike Youngstrom <youngm@...>

Great release Shannon! I've been waiting for relational db support before
we started using the routing api. Do you consider mysql/postresql support
production ready with this release or is it still beta/alpha like Diego's
relational support? Or is it the only option going forward with 0.141.0?


On Wed, Nov 2, 2016 at 7:31 PM, Shannon Coen <scoen(a)> wrote:

Today we released routing-release v0.141.0 with support for a
zero-downtime migration from etcd to mysql or postgresql as the backing
store for the routing-api. We changed our data store because the provided
way to enable TLS on etcd without downtime was to delete data from etcd,
and we require persistence. Also, it was suggested by the team that
maintains the etcd release that we should not rely on it for persistence.

Also included in this release:
- we've fixed a bug in our support of Zipkin tracing; this should be the
minimum version to use for that feature.
- enhancements to routing-acceptance-tests to support Google's HTTP load
balancer, which is apparently very opinionated in its interpretation of REST

For full release notes, see

Questions, feedback? Visit us in at #routing.


Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.

Join { to automatically receive all group messages.