github cloudfoundry/routing-release 0.180.0

latest releases: v0.237.0, 0.237.0, v0.236.0...
5 years ago

Release Highlights

  • Operator can see a log message that indicates the number of tries when the Gorouter fails to connect to a backend in the gorouter.log details
  • Golang has been updated to 1.10.3 for all routing components details here and here
  • Release author can now specify an IP for the route-registrar using the job spec. If a host is not found in the job spec it will default to the IP of the VM the route-registrar is running on details

Using BPM for routing components

  • We are now using BPM for gorouter details
  • We are now using BPM for routing-api details
  • We are now using BPM for route_registrar details

Note: BPM needs to be colocated on the VM for the components that are using BPM. If you are using cf-deployment, BPM is already colocated on the bosh deployed VMs, but if you are not using cf-deployment you would have to colocate the BPM job on the component VMs for gorouter, routing-api and route-registrar.

Bug fixes:

  • Fixed a issue where query parameters were not sent to the application when preceded by a // anywhere in the URL. Now when the request URL includes a //, the query parameters are sent to the application by the Gorouter details
  • Fixed an issue with symlinks to enable bosh-cli v5.x to work with routing-release details
  • PID files are being deleted when the Gorouter stops details

Known Issues

  • Due to the enabling of BPM in the gorouter job, if router.enable_access_log_streaming is set to true the gorouter job will fail to start. To get around this, you can set router.enable_access_log_streaming: false if you also have router.write_access_logs_locally: true. If you didn't previously write access logs to disk, then you'll want to keep an eye on disk usage. We'll plan to fix this behavior in the next release.

Don't miss a new routing-release release

NewReleases is sending notifications on new releases.