0.133.0

Note: final release is in routing-release/releases/routing/routing-0.133.0.yml. In subsequent releases this has been symlinked back to routing-release/releases

• Release renamed to routing-release details
• Some processes no longer run as root [details, more details]
• Unused logging properties have been removed details
• Gorouter source has been moved to this release and is symlinked into cf-release details
• Remove unused golang 1.4 package details
• TCP Routes are now pruned from TCP Router on a TTL when Routing API is unavailable, to prevent requests from being routed to the wrong backends details
• When registering routes with Routing API, a TTL can be optionally specified (defaults to 120s) details
• TCP Routes are now pruned from Routing API if client ceases to heartbeat route registration, to prevent requests from being routed to the wrong backends details
• TCP Router will only overwrite data received in periodic bulk fetches with buffered events if events are newer details
• Log level can be configured for routing api using a manifest property details
• Documented use of modification tags for router authors to reconcile data received from events and bulk fetch endpoints Additional Routing API docs details

Manifest Property Changes

0.126.0	0.133.0
added	routing-api.log_level
added	router.tcp_emitter.route_ttl
acceptance_tests.bbs.api_location	removed
acceptance_tests.bbs.ca_cert	removed
acceptance_tests.bbs.client_cert	removed
acceptance_tests.bbs.client_key	removed
acceptance_tests.bbs.require_ssl	removed

Dependencies

cf-release v236
diego-release 0.1468.0
cf CLI 6.17

0.126.0

Golang has been updated to 1.5.4 to address vulnerabilities in 1.5.3

Dependencies

cf-release v236
diego-release 0.1468.0
cf CLI 6.17

0.123.0

This release delivers MVP support for TCP Routing when deployed alongside cf-release and diego-release.

• All components are now highly available and horizontally scalable epic
• TCP Router and TCP Emitter cache OAuth tokens from UAA to communication with Routing API; Routing API validates tokens locally and fetches verification key from UAA automatically epic
• All components communicate with UAA internally over TLS epic
• Operator can now configure the range of ports that Cloud Controller will use when developers create TCP routes details

Consolidating Routing components into this release

• Routing API is now deployed with this release, not with cf-release details
• cf-tcp-acceptance-tests repo renamed to cf-routing-acceptance-tests details
• Routing API acceptance tests moved to cf-routing-acceptance-tests details

Instrumentation and Monitoring (in progress)

• Additional metrics for Routing API are now emitted via firehose details
• golang process metrics for all components are now emitted via firehose details

CLI

• Routing API CLI is now a submodule of this release details
• New stable Routing API CLI supports skip-ssl-validation details

Misc

• Routing components have been upgraded to golang 1.5.3 details
• bosh-lite manifest generation is now consistent with cf-release details
• This release and cf-mysql-release can now both be deployed to boshlite without IP collision details
• Consul agent updated to use new internal hostname details
• Acceptance tests use CC API instead of Diego details

Dependencies

cf-release v236
diego-release 0.1468.0
cf CLI 6.17

Do not use

0.122.0

Create final release 0.122.0

0.121.0

• TCP Routers are now automatically updated by creating/updating/deleting LRPs via Diego. The routers fetch their configuration from Routing API; TCP emitter watches Diego and populates Routing API epic
• Routing components are highly available and horizontally scalable (in progress) epic

Misc

• Creating a tcp route requires a router group guid; if diego client specifies a router group guid with tcp route, tcp-emitter will send it to the routing api details
• Operator can now disable the requirement for authentication on the routing api; components will not attempt to contact uaa details
• When updating an LRP, requests are no longer routed to the backends removed from a route details
• routing API can be use to delete one or more tcp route mappings details
• When deleting an LRP with a tcp routes, backends are no longer accessible by the route details

0.118.0

• TCP Router and TCP Emitter now use Routing API from cf-release for dynamic configuration of TCP routing. tcp-routing-api has been eliminated.
• Known issue: This final release will fail to deploy if diego-release is configured with properties.bbs.require_ssl: false. The default value for that property in diego-release is true.