v1.17.8

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

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

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

This release contained no user-facing changes.

v1.16.20

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

New Features

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

v1.18.0-beta18

Helm Changes

• helm/gloo: introduce component label for grouping resources

Introduces a gloo.solo.io/component label to group Helm resources
that are associated with a given component. This is required by
downstream projects that use Helm as a templating engine to be able
to group resources associated with a component and customize their
behavior. This change groups resources related required by the
certgen component using the new label. (solo-io/solo-projects#6824)

Fixes

• Give each test summary artifact a unique name and refactor summary code into reusable package (solo-io/solo-projects#6646)

v1.17.7

This release contained no user-facing changes.

v1.17.6

This release contained no user-facing changes.

v1.18.0-beta17

New Features

• Add new API fields to AI Semantic Caching API.
• Mode field to control whether the proxy will cache responses, or only read.
• scoreThreshold field to control the minimum similarity score required for a cached response to be used. (solo-io/solo-projects#6783)

Fixes

• Don't multiply custom filters by plugins. (#9915)
• Fix a bug where an empty GWP seg faults. (#9922)