Gloo Versions Save

New Features

• Adds a new Listener level access log option. Previously Edge was able to configure Proxy level logging for TCP proxies and HTTPConnectionManager(hcm) level logging for HTTP. With this change there is a new listeneroption that will configure http listener level logs. While http hcm has generally more useful logs there are certain logging command operators that are not usable at certain levels. The old version of logging and the new version are also both configurable concurrently but will have a higher performance overhead. This change also introduces a new warning log for command operators that are not useful for a given levels. For now this warning is purely a log line to reduce thrash before hardening these checks. (https://github.com/solo-io/gloo/issues/8438)

Fixes

• Fix a bug that caused the validation server to incorrectly reject deletion operations for Kube type Upstreams (https://github.com/solo-io/gloo/issues/6543)

Dependency Bumps

• onsi/ginkgo/v2 has been upgraded to v2.17.0.
• onsi/gomega has been upgraded to v1.30.0.
• golang.org/x/crypto has been upgraded to v0.18.0.
• golang.org/x/sync has been upgraded to v0.6.0.
• golang.org/x/tools has been upgraded to v0.17.0.

New Features

• Introduce VirtualHostOption plugin for the Kubernetes Gateway API integration. This plugin will honor VirtualHostOption resources and when translating K8s Gateway resources and apply their contents to the appropriate sections of the final proxy object. (https://github.com/solo-io/solo-projects/issues/6002)

Fixes

• Fix controller plumbing to watch for and reconcile changes to VirtualHostOption resources in the Kubernetes Gateway controller (https://github.com/solo-io/solo-projects/issues/6002)

Dependency Bumps

• solo-io/envoy-gloo has been upgraded to v1.29.3-patch1.
• golang/go has been upgraded to v1.22.2.
• solo-io/cloud-builders has been upgraded to v0.9.1.

Fixes

• Revert "Hardcode Envoy's reloadable feature for TE header sanitization to false" (#9307) (https://github.com/solo-io/gloo/issues/9232)

Dependency Bumps

• solo-io/envoy-gloo has been upgraded to v1.26.8-patch1.
• solo-io/cloud-builders has been upgraded to v0.7.6.

Dependency Bumps

• solo-io/envoy-gloo has been upgraded to v1.27.4-patch1.
• golang/go has been upgraded to v1.21.9.
• solo-io/cloud-builders has been upgraded to v0.8.4.

Fixes

• Simplify the control plane helm API for the Kubernetes Gateway integration, and remove unused values. There is now just one helm flag (kubeGateway.enabled) that is used to enable/disable the Kubernetes Gateway integration. (https://github.com/solo-io/solo-projects/issues/5856)

New Features

• RouteOption resources used for policy attachment (via targetRef) will now have their status correctly set based on the result of translation (https://github.com/solo-io/solo-projects/issues/5934)
• Introduce targetRef field to VirtualHostOption resource. This will allow users of the Kubernetes Gateway API to specify which Gateway resource, and optionally which Listeners on that resource will be affected by the VirtualHostOption (https://github.com/solo-io/solo-projects/issues/6002)

This release is building...

New Features

• Add new GatewayParameters CRD to allow configuration of dynamically provisioned proxies in Gloo Gateway. (https://github.com/solo-io/solo-projects/issues/5909)

Fixes

• Restrict the certgen job's secret access to just the gloo installation namespace. The certgen job does not require cluster wide access to secrets as it only manages secrets within the gloo installation namespace. (https://github.com/solo-io/gloo/issues/5960)

Dependency Bumps

• solo-io/skv2 has been upgraded to v0.36.5.

New Features

• Support policy attachment for RouteOption resources (https://github.com/solo-io/solo-projects/issues/5714)

Fixes

• Hardcode Envoy's reloadable feature for TE header sanitization to false. This feature as it exists in 1.29.2 breaks gRPC upstreams whose client library expects TE: trailers. This hardcode will be removed when Gloo Edge depends upon 1.29.3, which has a fix for the gRPC case but is currently unreleased. (https://github.com/solo-io/gloo/issues/9232)
• The Gloo Gateway deployer now gets the xDS host and port from the gloo service, instead of using potentially incorrect values. (https://github.com/solo-io/solo-projects/issues/5949)