Skip to content

Releases: solo-io/gloo

v1.18.0-beta12

31 Jul 14:56
cc31de1
Compare
Choose a tag to compare

Dependency Bumps

  • solo-io/envoy-gloo has been upgraded to v1.30.4-patch2.

New Features

  • gateway2/route-options: merge extensionRef based attachments

Enables merging of multiple ExtensionRef based RouteOption
attachments for a rule within an HTTPRoute. (solo-io/solo-projects#6675)

v1.18.0-beta11

26 Jul 18:09
02d48c6
Compare
Choose a tag to compare

Fixes

There's a bug where if a child route contains an invalid rule (rule
not matching the parent matcher), then even though the matcher is
discarded, the rule with an empty matcher but valid backendRef
is returned by GetDelegatedRoutes(). The result is that a /
route is programmed for such an invalid route rule. A more
precise fix is to also prune the rules that do not have a valid
matcher so that we do not rely on the translator to interpret
a route without a valid matcher as '/', which could be an alternative
fix though fragile.

The essence of this fix is to prune both the rules and matches
field on the child route when we process it in the context of the
parent matcher, so that:

  1. invalid matchers on the child route are discarded
  2. invalid rules (no valid child matchers) are also discarded

Previously, 2. was missing so a child route with a rule without
a matcher was configured, which results in a / route being exposed
for the corresponding backendRef. (solo-io/solo-projects#6621)

v1.17.1

23 Jul 15:52
ac58c94
Compare
Choose a tag to compare

Fixes

  • Fix a bug where the service and function names of a discovered gRPC service are not printed in JSON and YAML
    output when running glooctl get upstreams (#9743)

v1.15.30

23 Jul 20:16
9499985
Compare
Choose a tag to compare

Fixes

  • Fix a bug where the service and function names of a discovered gRPC service are not printed in JSON and YAML
    output when running glooctl get upstreams (#9743)
  • Infer the gloo deployment name in cases where the deployment name is not the default gloo. The gloo deployment is identified by the gloo=gloo label. (#9163)
  • Optimizes the glooctl check command by reducing the time taken to check resources by almost half in large environments consisting of over 500 namespaces (#9673)
  • Fix a bug where the service and function names of a discovered gRPC service are not printed when running glooctl get upstreams (#9644)

v1.18.0-beta10

23 Jul 13:12
3ad2c1b
Compare
Choose a tag to compare

Fixes

  • Add AssertEventualCurlError assertion for kubernetes e2e tests to assert that a curl command eventually fails. This is useful for validating that a route is not reachable/a deletion has taken effect. (solo-io/solo-projects#6437)
  • Fix a bug where the service and function names of a discovered gRPC service are not printed in JSON and YAML
    output when running glooctl get upstreams (#9743)

v1.18.0-beta9

19 Jul 15:03
cb4f56c
Compare
Choose a tag to compare

New Features

Fixes

  • Clarify the inheritance behavior of CORS APIs defined on the VirtualHost and Route level. Previously, there was a claim that when properties were defined at both levels, they were merged. However, the accurate behavior is that RouteOptions fields entirely override VirtualHostOptions when RouteOptions are defined. (#8115)

v1.18.0-beta8

17 Jul 20:54
0cbdbd7
Compare
Choose a tag to compare

Fixes

  • Fix regex safety check for CORS allowed origins. Other instances in gloo already checked the regex either through compile or envoy validate. (#7524)
  • Resolves issue of HTTPS listeners not aggregating appropriately when defined using the same port on a kube gateway. (solo-io/solo-projects#6559)

v1.17.0

15 Jul 18:32
751e637
Compare
Choose a tag to compare

Dependency Bumps

  • solo-io/envoy-gloo has been upgraded to v1.30.4-patch1.

Fixes

  • Fix regex safety check for CORS allowed origins. Other instances in gloo already checked the regex either through compile or envoy validate. (#7524)

v1.16.18

15 Jul 18:36
5c3ca79
Compare
Choose a tag to compare

Fixes

  • Fix regex safety check for CORS allowed origins. Other instances in gloo already checked the regex either through compile or envoy validate. (#7524)
  • Infer the gloo deployment name in cases where the deployment name is not the default gloo. The gloo deployment is identified by the gloo=gloo label. (#9163)
  • Optimizes the glooctl check command by reducing the time taken to check resources by almost half in large environments consisting of over 500 namespaces (#9673)
  • Fix a bug where the service and function names of a discovered gRPC service are not printed when running glooctl get upstreams (#9644)

v1.17.0-rc12

12 Jul 19:33
f37eaf2
Compare
Choose a tag to compare

Fixes

  • Resolves issue of HTTPS listeners not aggregating appropriately when defined using the same port on a kube gateway. (solo-io/solo-projects#6559)