cloudfoundry/routing-release 0.141.0

on GitHub

• Routing API now supports mysql or postgresql as datastore instead of etcd. When routing_api.sqldb property is configured, data will be migrated from etcd. Routing API will continue watching etcd for new data to migrate until it loses connection with etcd (if that component is rolled for a deploy) or the routing_api.etcd property is removed with a subsequent deploy. Property routing_api.etcd is now optional when routing_api.sqldb is present.
• Fixed bug for Zipkin tracing support: header X-B3-ParentSpanId is no longer sent when request does not include headers X-B3-TraceId and X-B3-SpanId details
• Fixed bug introduced in 0.139.0: when router.force_forwarded_proto_https: false gorouter once again sends X-Forwarded-Proto: https to backends when request was received over TLS details
• Routing acceptance tests no longer test routing api endpoints for http routes by default (as they are experimental and as yet unused by CF) details
• Routing API client no longer sends body null with GET requests details
• Gorouter now logs the destination ip and port in access logs details
• Manifest generation scripts now pulls etcd certificate properties from cf-release for the metron agent colocated with routing components, so that it can communicate with etcd when it requires TLS details
• scripts/update now exits fast when permission denied details

Known Issues

• Manifest generation scripts insert two lines of nonsense at the top of the manifest file, causing deploy to fail. Remove these two lines and deploy will succeed. Will be fixed in the next release!

Manifest Property Changes

routing_api

tcp_emitter

acceptance_tests