Releases: cloudfoundry/routing-release
Releases · cloudfoundry/routing-release
0.313.0
0.313.0
Release Date: October 02, 2024
Changes
✨ Built with go 1.23.1
Full Changelog: v0.312.0...v0.313.0
Resources
Full Changelog: v0.312.0...v0.313.0
Contributors
hoffmaen
Assets 3
0.312.0
0.312.0
Release Date: September 30, 2024
Changes
- Upgrade to Go 1.23
- Make ReadHeaderTimeout configurable in release
- fix: bump minimum go version to 1.23 for partitioned cookies (https://github.com/cloudfoundry/routing-release/pull/437[)](https://github.com/cloudfoundry/routing-release/commit/f8b9f683418a8c458db2eb139d1bfd045986c11e)
- Various Minor Bumps
Bosh Job Spec changes:
diff --git a/jobs/acceptance_tests/spec b/jobs/acceptance_tests/spec
index 8122ddaf..51a81762 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.22-linux
+ - golang-1.23-linux
- acceptance_tests
- rtr
- cf-cli-8-linux
diff --git a/jobs/gorouter/spec b/jobs/gorouter/spec
index 60c7b520..c7896a27 100644
--- a/jobs/gorouter/spec
+++ b/jobs/gorouter/spec
@@ -364,6 +364,9 @@ properties:
Generally, this timeout must be greater than that of the load balancer. As examples, GCP HTTP(S) load balancer has a default timeout of 600 seconds so a value greater than 600 is recommended and AWS ELB has a default timeout of 60 seconds so a value greater than 60 is recommended.
However, depending on the IaaS, this timeout may need to be shorter than the load balancer's timeout, e.g., Azure's load balancer times out at 240 seconds (by default) and GCP TCP load balancer times out at 600 seconds without sending a TCP RST to clients, so a value lower than this is recommended in order to force it to send the TCP RST.
default: 900
+ router.read_header_timeout:
+ description: "The amount of time allowed to read request headers."
+ default: 0
router.backends.max_conns:
description: "Maximum concurrent TCP connections per backend. When set to 0 there is no limit"
default: 500
diff --git a/jobs/smoke_tests/spec b/jobs/smoke_tests/spec
index 02edfd9d..4ea8eb07 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.22-linux
+ - golang-1.23-linux
- acceptance_tests
- cf-cli-8-linux
✨ Built with go 1.23.1
Full Changelog: v0.311.0...v0.312.0
Resources
0.311.0
0.311.0
Release Date: September 12, 2024
Changes
- Fix route-registrar dynamic config YAML field names to match JSON names
✨ Built with go 1.22.7
Full Changelog: v0.310.0...v0.311.0
Resources
0.310.0
0.310.0
Release Date: September 09, 2024
Changes
- dep: bump gopkg.in/yaml from v2 to v3; adjusted submodules listed in routing-release#435
- minor dependency bumps
✨ Built with go 1.22.7
Full Changelog: v0.309.0...v0.310.0
Resources
0.309.0
0.309.0
Release Date: September 06, 2024
Changes
- Dependency bumps
✨ Built with go 1.22.7
Full Changelog: v0.308.0...v0.309.0
Resources
0.308.0
0.308.0
Release Date: September 04, 2024
Changes
- Route Registrar now allows hosts to be configured per route
- By default it will use the top level host config
✨ Built with go 1.22.6
Full Changelog: v0.307.0...v0.308.0
Resources
0.307.0
0.307.0
Release Date: August 27, 2024
Changes
- Bump healthchecker-boshrelease vendored packages
✨ Built with go 1.22.6
Full Changelog: v0.306.0...v0.307.0
Resources
0.306.0
0.306.0
Release Date: August 26, 2024
Changes
- 🐛Fixes a bug where TCP routes were incorrectly detected as existing records in routing-api when the only difference between the new route and existing record was that the SNI Hostname or TLS TCP Port were different. This resulted in backends for TLS TCP Routes being ignored in certain scenarios.
✨ Built with go 1.22.6
Full Changelog: v0.305.0...v0.306.0
Resources
0.305.0
0.305.0
Release Date: August 23, 2024
Changes
- Route-registrar can dynamically scan and register routes at paths matching
route_registrar.dynamic_config_globs
Bosh Job Spec changes:
diff --git a/jobs/route_registrar/spec b/jobs/route_registrar/spec
index feafaf10..4f887265 100644
--- a/jobs/route_registrar/spec
+++ b/jobs/route_registrar/spec
@@ -94,6 +94,10 @@ properties:
route_registrar.routing_api.server_ca_cert:
description: "Routing API Certificate Authority"
+ route_registrar.dynamic_config_globs:
+ description: "Files matching the globs contain routes configuration that will be loaded dynamically. Parent directory must exist for bpm to mount it."
+ default: [/var/vcap/jobs/*/config/route_registrar/config.yml]
+
route_registrar.routes:
description: |
(required, array of objects): Routes that will be registered
✨ Built with go 1.22.6
Full Changelog: v0.304.0...v0.305.0
Resources
0.304.0
0.304.0
Release Date: August 13, 2024
Changes
- Addresses issues with routing-api DB migration logic to fix the following bugs:
- 🐛 Failed DB migrations would not re-run without manual intervention in the database
- 🐛 DB migrations could run prior to the active routing-api server receiving code updates
- 🐛 Failed DB migrations did not result in BOSH deployment failures
- 🐛Works around an issue with Gorm + the V6 schema changes for TLS TCP Routing that did not always get applied properly.
✨ Built with go 1.22.6
Full Changelog: v0.303.0...v0.304.0