Release Highlights
-
Platform Operators can now configure the database max idle and max open connections along with the connection timeout for routing-api details
-
Application Developers can see metrics that help them more easily determine if latency is coming from the gorouter or their application details
-
Platform Operators can now leverage
jq
on the router vm to debug more easily details -
Application Developers can leverage w3c trace context to experience better:
- Visibility into the behavior of distributed applications
- Management of micro-service applications details -
Routing Release is built with Go 1.13, which includes TLS 1.3. However, TLS 1.3 is now turned off for now for the TCP-Router endpoints as a result of this issue: golang/go#35722
Manifest Property Changes
Job | Property | 0.195.0 Default | 0.196.0 Default |
---|---|---|---|
gorouter | tracing.enable_w3c
| Did Not Exist | False |
gorouter | tracing.w3c_tenant_id
| Did Not Exist | "" |
routing_api | routing_api.sqldb.max_open_connections
| Did Not Exist | 200 |
routing_api | routing_api.sqldb.max_idle_connections
| Did Not Exist | 10 |
routing_api | routing_api.sqldb.connections_max_lifetime_seconds
| Did Not Exist | 3600 |