Releases: cloudfoundry/routing-release
Releases · cloudfoundry/routing-release
0.264.0
Known Issues
⚠️ This release is susceptible to the issue described in CVE-2023-20882. This issue is fixed in routing-release 0.266.0.⚠️ This release is vulnerable to this known issue around handling expect 100-continue responses. This issue is fixed in routing-release 0.274.0- We recommend skipping this version and upgrading to 0.274.0 instead.
Changes
- Addresses the issue in routing-release 0.263.0 where
bosh export-releaseswould fail to compile theacceptance-testspackage.
✨ Built with go 1.20.3
Full Changelog: v0.263.0...v0.264.0
Resources
0.263.0
Known Issues
⚠️ This release is susceptible to the issue described in CVE-2023-20882. This issue is fixed in routing-release 0.266.0.⚠️ This release is vulnerable to this known issue around handling expect 100-continue responses. This issue is fixed in routing-release 0.274.0- We recommend skipping this version and upgrading to 0.274.0 instead.
Changes
- 🐛Fixed a bug present since v0.262.0 that caused CATs to intermittently fail on apps using
ncas their server. - 🐛Bumped haproxy to 2.7.6 in cf-tcp-router, to resolve a bug preventing haproxy from properly transferring open connections to the new haproxy process when a reload occurred - haproxy/#1883
✨ Built with go 1.20.3
Full Changelog: v0.262.0...v0.263.0
Resources
0.262.0
Known Issues
⚠️ This release is susceptible to the issue described in CVE-2023-20882. This issue is fixed in routing-release 0.266.0.⚠️ This release is vulnerable to this known issue around handling expect 100-continue responses. This issue is fixed in routing-release 0.274.0- We recommend skipping this version and upgrading to 0.274.0 instead.
Changes
- 🐛Fixes the of golang has a known issue that causes backend request failures which previously returned 496, 499, 503, 525, or 526 to instead return a 502. Additionally stale routes may not have been pruned properly. Thanks @domdom82!!
- 🚗Gorouter now retries requests which fail prior to any HTTP content being sent (since no backend received the HTTP content, they're by definition retriable). Thanks for the PR. Thanks @maxmoehl and @domdom82!!
✨ Built with go 1.20.2
Full Changelog: v0.261.0...v0.262.0
Resources
Contributors
domdom82 and maxmoehl
Assets 3
0.261.0
Known Issues
⚠️ This release is susceptible to the issue described in CVE-2023-20882. This issue is fixed in routing-release 0.266.0.⚠️ This release is vulnerable to this known issue around handling expect 100-continue responses. This issue is fixed in routing-release 0.274.0- We recommend skipping this version and upgrading to 0.274.0 instead.
Changes
- Bug fix: add healthcheck to routing-api for route-registrar
Bosh Job Spec changes:
diff --git a/jobs/routing-api/spec b/jobs/routing-api/spec
index 5717f88f..f6a2175d 100644
--- a/jobs/routing-api/spec
+++ b/jobs/routing-api/spec
@@ -6,12 +6,15 @@ templates:
uaa_ca.crt.erb: config/certs/uaa/ca.crt
routing-api.yml.erb: config/routing-api.yml
+ routing_api_health_check.erb: bin/routing_api_health_check
locket_ca.crt.erb: config/certs/locket/ca.crt
locket_client.crt.erb: config/certs/locket/client.crt
locket_client.key.erb: config/certs/locket/client.key
api_mtls_client_ca.crt.erb: config/certs/routing-api/client_ca.crt
+ api_mtls_client.crt.erb: config/certs/routing-api/client.crt
+ api_mtls_client.key.erb: config/certs/routing-api/client.key
api_mtls_server.crt.erb: config/certs/routing-api/server.crt
api_mtls_server.key.erb: config/certs/routing-api/server.key
@@ -107,6 +110,13 @@ properties:
routing_api.mtls_client_key:
description: "Routing API client key (provided to clients by bosh link)"
+ routing_api.health_check_timeout_per_retry:
+ default: 2
+ description: "Maximum health check timeout (in seconds) for each retry attempt in the Routing API's route registration health check"
+ routing_api.health_check_total_timeout:
+ default: 6
+ description: "Maximum health check timeout (in seconds). Health checks will be retried until this time limit is reached. This should be less than or equal to your route_registrar.routes.api.health_check.timeout"
+
metron.port:
description: "The port used to emit dropsonde messages to the Metron agent."
default: 3457
✨ Built with go 1.20.2
Full Changelog: v0.260.0...v0.261.0
Resources
0.260.0
Known Issues
⚠️ This release is susceptible to the issue described in CVE-2023-20882. This issue is fixed in routing-release 0.266.0.⚠️ This release is vulnerable to this known issue around handling expect 100-continue responses. This issue is fixed in routing-release 0.274.0- We recommend skipping this version and upgrading to 0.274.0 instead.
Changes
- Dependency updates (cf cli, healthchecker, golang)
- Many CI Updates - Thanks @jrussett!
- 🐛[#310]The routing_utils route loader now sets the route service url when loading. Thanks @domdom82 !
- 🐛Two issues in route_registrar were fixed that led to routes expiring and then being re-registered with the same details:
- Starting in v0.245.0, route_registrar no longer retried UAA connections when getting a token from UAA. Instead, the failure would cause route_registrar to restart, and reset it's emitter intervals.
- The built in route expiry has been increased from RegistrationInterval + 2 seconds to 2.1 * RegistrationInterval. This prevent routes from expiring during the course of a route_registrar restart.
- 🐛If tcp_router received routing events during its BulkSync cycle, it would always rewrite the haproxy configuration, and reload the haproxy process. This would occur regardless of whether the events required a new haproxy config. It now only updates the config + reloads haproxy if changes are necessary.
✨ Built with go 1.20.2
Full Changelog: v0.259.0...v0.260.0
Resources
Contributors
domdom82 and jrussett
Assets 3
0.259.0
Known Issues
⚠️ This release is susceptible to the issue described in CVE-2023-20882. This issue is fixed in routing-release 0.266.0.⚠️ This release is vulnerable to this known issue around handling expect 100-continue responses. This issue is fixed in routing-release 0.274.0- We recommend skipping this version and upgrading to 0.274.0 instead.
Changes
- No changes from last version.
- Fixing CI so that artifacts are generated correctly for github release.
✨ Built with go 1.20.1
Full Changelog: v0.258.0...v0.259.0
Resources
0.258.0
Known Issues
⚠️ This release is susceptible to the issue described in CVE-2023-20882. This issue is fixed in routing-release 0.266.0.⚠️ This release is vulnerable to this known issue around handling expect 100-continue responses. This issue is fixed in routing-release 0.274.0- We recommend skipping this version and upgrading to 0.274.0 instead.
Changes
- Update healthchecker to 0.4.0
- Increase startup delay default to 30 seconds PR
- Upgrade golang to 1.20.1
Bosh Job Spec changes:
diff --git a/jobs/acceptance_tests/spec b/jobs/acceptance_tests/spec
index 65bf4c30..6a73b9ae 100644
--- a/jobs/acceptance_tests/spec
+++ b/jobs/acceptance_tests/spec
@@ -7,7 +7,7 @@ templates:
bpm.yml.erb: config/bpm.yml
packages:
- - golang-1.19-linux
+ - golang-1.20-linux
- acceptance_tests
- rtr
- cf-cli-6-linux
diff --git a/jobs/smoke_tests/spec b/jobs/smoke_tests/spec
index b16357ed..0426dc99 100644
--- a/jobs/smoke_tests/spec
+++ b/jobs/smoke_tests/spec
@@ -7,7 +7,7 @@ templates:
bpm.yml.erb: config/bpm.yml
packages:
- - golang-1.19-linux
+ - golang-1.20-linux
- acceptance_tests
- cf-cli-6-linux
✨ Built with go 1.20.1
Full Changelog: v0.257.0...v0.258.0
Resources
0.257.0
Changes
- Bumped to build with golang 1.19.6
✨ Built with go 1.19.6
Full Changelog: v0.256.0...v0.257.0
Resources
0.256.0
Changes
- Update healthchecker in release to stable version
✨ Built with go 1.19.5
Full Changelog: v0.255.0...v0.256.0
Resources
0.255.0
Upgrade healthchecker in release. In order to limit the scope of packages brought in with the introduction of http healthchecker, we migrated the healthchecker package out of cf-networking-helpers into its own release.
Full Changelog: 0.254.0...v0.255.0
✨ Built with go 1.19.5