Skip to content

Releases: solo-io/gloo

v1.18.0-beta23

27 Sep 15:11
2a290f0
Compare
Choose a tag to compare

Dependency Bumps

  • solo-io/cloud-builders has been upgraded to 0.10.1.
  • golang/go has been upgraded to go1.23.1.
  • solo-io/go-utils has been upgraded to 0.27.0.

Helm Changes

  • Automatically set the GOMAXPROCS environment variable in the gloo and discovery pods when CPU resource limits are set (via the resources.limits.cpu deployment helm value). Automatically set the GOMEMLIMIT environment variable in the gloo and discovery pods when memory resource limits are set (via the resources.limits.memory deployment helm value). These may help limit CPU/memory usage when resource limits are set on the pods. (#10062)

New Features

v1.17.10

24 Sep 19:26
df90c9d
Compare
Choose a tag to compare

This release contained no user-facing changes.

v1.17.9

23 Sep 20:06
2362f6f
Compare
Choose a tag to compare

Dependency Bumps

  • solo-io/solo-kit has been upgraded to v0.35.4.

Fixes

  • Adds a new field watchNamespaceSelectors to the settings CR. This allows users to specify namespaces to watch based on label selectors. The watchNamespaces field will override this if specified. (#9274)
  • Adds a new helm value settings.watchNamespaceSelectors. This allows users to specify namespaces to watch based on label selectors that can be specified via settings.watchNamespaceSelectors.matchLabels for an exact label match and settings.watchNamespaceSelectors.matchExpressions for more generic requirements. The settings.watchNamespaces field will override this if specified. (#9274)

v1.18.0-beta22

17 Sep 21:17
d71b7bb
Compare
Choose a tag to compare

Dependency Bumps

  • solo-io/cloud-builders has been upgraded to 0.10.1.
  • golang/go has been upgraded to go1.23.1.

New Features

Fixes

  • Increase timeout/retries for glooctl check when connecting to the gateway using port forwarding. (#10020)
  • Fixes an issue on upgrades to 1.17+ where persistproxyspec was set to true. Persist proxy spec is configured in helm via gateway.persistProxySpec or in ee gloo.gateway.persistProxySpec (#9968)
  • Plugs a gap where go would check a secret for validity per spec but Envoy is more aggressive. For example a TLS secret with a certChain that contains an invalid PEM block will be rejected by Envoy but not Go. Prior to this PR these types of secrets would be accepted by Gloo and nacked by Envoy. (solo-io/solo-projects#6772)

v1.17.8

16 Sep 23:39
e658203
Compare
Choose a tag to compare

Dependency Bumps

  • solo-io/cloud-builders has been upgraded to 0.9.3.
  • golang/go has been upgraded to go1.22.7.

Fixes

  • Increase timeout/retries for glooctl check when connecting to the gateway using port forwarding. (#10020)
  • Fixes an issue on upgrades to 1.17+ where persistproxyspec was set to true. Persist proxy spec is configured in helm via gateway.persistProxySpec or in ee gloo.gateway.persistProxySpec (#9968)
  • Plugs a gap where go would check a secret for validity per spec but envoy is more aggressive. For example a tls secret with a certchain that contains an invalid pem block will be rejected by envoy but not go. Prior to this pr these types of secrets would be accepted by gloo and nacked by envoy. (solo-io/solo-projects#6772)

v1.18.0-beta21

11 Sep 18:22
f8ad1b1
Compare
Choose a tag to compare

Dependency Bumps

  • solo-io/cloud-builders has been upgraded to 0.9.3.
  • solo-io/cloud-builders has been upgraded to 0.9.3.
  • solo-io/cloud-builders has been upgraded to 0.9.3.
  • solo-io/cloud-builders has been upgraded to 0.9.3.
  • golang/go has been upgraded to go1.22.7.

New Features

  • Adds new validationPolicy option for JWT configuration to allow configuring ALLOW_MISSING if token is missing, request is still accepted. The existing API flag allow_missing_or_failed is not sufficient for this use case. (#8728)
  • Add API support for Azure OpenAI Token based auth with the AI Gateway. (solo-io/solo-projects#6856)
  • Introduce a new DirectResponse v1alpha1 API to allow users to configure direct response routes with the Kubernetes Gateway API integration. Now, users can configure a direct response action for an HTTPRoute via an extensionRef filter to this new API. (#9774)
  • Expose max_buffered_{rx/tx}_bytes, record_headers_received_time and record_downstream_connection settings for the Tap filter config. (#9656)

v1.15.31

06 Sep 18:42
4c0de81
Compare
Choose a tag to compare

Helm Changes

  • New field gateway.validation.warnMissingTlsSecret controls whether missing TLS secrets referenced in SslConfig and UpstreamSslConfig will be treated as a warning instead of an error during validation. Defaults to false. This field has no effect if allowWarnings is false or acceptAllResources is true. (#6957)

Fixes

  • Fix for issue where a missing TLS secret was treated by validation as an error, potentially bringing down the entire HTTPS gateway if the gloo pod restarts while in this bad state. This is a breaking change in the default behavior of validation. To enable this behavior, use the helm setting gateway.validation.warnMissingTlsSecret=true or the same field on the Settings CR. This field has no effect if allowWarnings is false or acceptAllResources is true. (#6957)

v1.18.0-beta20

05 Sep 16:37
4262b64
Compare
Choose a tag to compare

This release contained no user-facing changes.

v1.16.20

06 Sep 18:40
4e68822
Compare
Choose a tag to compare

Helm Changes

  • New field gateway.validation.warnMissingTlsSecret controls whether missing TLS secrets referenced in SslConfig and UpstreamSslConfig will be treated as a warning instead of an error during validation. Defaults to false. This field has no effect if allowWarnings is false or acceptAllResources is true. (#6957)

Fixes

  • Fix for issue where a missing TLS secret was treated by validation as an error, potentially bringing down the entire HTTPS gateway if the gloo pod restarts while in this bad state. This is a breaking change in the default behavior of validation. To enable this behavior, use the helm setting gateway.validation.warnMissingTlsSecret=true or the same field on the Settings CR. This field has no effect if allowWarnings is false or acceptAllResources is true. (#6957)

v1.18.0-beta19

03 Sep 15:13
4af3e46
Compare
Choose a tag to compare

New Features

  • Added support for route level JWT configuration by introducing new jwtProvidersStaged field on the RouteOptions. (solo-io/solo-projects#6541)