gloo

Helm Changes

• Fix indentation for custom HTTPS Gateway settings (https://github.com/solo-io/gloo/issues/5874)

New Features

• Validate the integrity of TLS secrets, allowing users to call glooctl check to identify bad TLS configuration (https://github.com/solo-io/gloo/issues/5662)

Fixes

• Fix TLS secret conversion. (https://github.com/solo-io/gloo/issues/5889)

Dependency Bumps

• solo-io/envoy-gloo has been upgraded to 1.20.0-patch3.

Helm Changes

• Fix indentation for custom HTTPS Gateway settings (https://github.com/solo-io/gloo/issues/5874)

New Features

• Allow for roles to chain assume up to 1 deep. This enables cross account role assumption The runtime gaurd envoy.reloadable_features.aws_lambda.sts_chaining can be set to 0 to reinstate prior behavior and to never chain. (https://github.com/solo-io/gloo/issues/5639)
• Add a helm option to support running the certgen job on upgrades and installs (https://github.com/solo-io/gloo/issues/4638)
• Validate the integrity of TLS secrets, allowing users to call glooctl check to identify bad TLS configuration (https://github.com/solo-io/gloo/issues/5662)

Fixes

• Fix TLS secret conversion. (https://github.com/solo-io/gloo/issues/5889)

New Features

• Adds support for the Envoy HTTP Connection Manager settings headers_with_underscores_action and max_requests_per_connection.
  Additionally, adds support for the HTTP Connection Manager allow_chunked_length setting and the cluster-level max_concurrent_streams setting (https://github.com/solo-io/gloo/issues/5762)

Fixes

• Gateways are no longer dependant on having an associated VirtualService to receive/clear their own resource statuses. (https://github.com/solo-io/gloo/issues/5578)
• Accept opaque header secrets in addition to gloo.solo.io/header. (https://github.com/solo-io/gloo/issues/5323)

New Features

• Accept opaque header secrets in addition to gloo.solo.io/header. (https://github.com/solo-io/gloo/issues/5323)
• Change oauth secret type from Opaque to extauth.solo.io/oauth (https://github.com/solo-io/gloo/issues/5323)

Fixes

• Gateways are no longer dependant on having an associated VirtualService to receive/clear their own resource statuses. (https://github.com/solo-io/gloo/issues/5578)

This release contained no user-facing changes.

New Features

• Added the ability to fully preserve the casing of headers (as opposed to normalizing to kebab-style-lowercase) (https://github.com/solo-io/gloo/issues/5522)

New Features

• Added the ability to fully preserve the casing of headers (as opposed to normalizing to kebab-style-lowercase) (https://github.com/solo-io/gloo/issues/5522)

Fixes

• Ensure that enterprise features, when used by an open source user, produce error messages (https://github.com/solo-io/gloo/issues/4020)
• Remove the Upgradable Plugin interface. This abstraction was a little leaky. Now we handle upgrading plugins in the enterprise application itself, as that is the source of truth for what should be upgraded. (https://github.com/solo-io/gloo/issues/4367)

This release contained no user-facing changes.

New Features

• Add the ability to record metrics tracking the configuration status of various resource types. By default, these metrics are not recorded; however, they can be enabled/configured via settings.observabilityOptions.configStatusMetricLabels. (https://github.com/solo-io/gloo/issues/3964)

New Features

• Add the ability to record metrics tracking the configuration status of various resource types. By default, these metrics are not recorded; however, they can be enabled/configured via settings.observabilityOptions.configStatusMetricLabels. (https://github.com/solo-io/gloo/issues/3964)

Fixes

• Add graphql CRD validation. If using helm upgrade to this version, this requires a re-install of the graphql schema CRD. (https://github.com/solo-io/solo-projects/issues/2948)
• When a Gateway with a HybridListener defined contained invalid Ssl configuration,
  a panic would occur while generating the FilterChain, preventing other updates
  from being processed by the control plane. (https://github.com/solo-io/gloo/issues/5785)
• Fix prepare-directories.sh for docker-compose use (https://github.com/solo-io/gloo/issues/5777)

Dependency Bumps

• solo-io/k8s-utils has been upgraded to v0.0.12.

Fixes

• When a Gateway with a HybridListener defined contained invalid Ssl configuration,
  a panic would occur while generating the FilterChain, preventing other updates
  from being processed by the control plane. (https://github.com/solo-io/gloo/issues/5785)
• Fix prepare-directories.sh for docker-compose use (https://github.com/solo-io/gloo/issues/5777)
• Update all references to v1beta1 packages, to ensure that ingress installation succeeds on Kube 1.22 (https://github.com/solo-io/gloo/issues/5523)

This release contained no user-facing changes.

New Features

• Add new HybridGateway Gateway type which wraps HTTP and TCP Gateways, allowing the user to expose multiple HTTP and/or TCP Gateway on a single port Per-request dynamic Gateway selection is determined by Matchers which enable finer control over Envoy FilterChainMatches (https://github.com/solo-io/gloo/issues/5324)

Dependency Bumps

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

New Features

• Alow for the new per route option on lambda invocation to act as if it was an ALB. This is intended to be used to ease migration from using ALB for lambda invocation to gloo. (https://github.com/solo-io/gloo/issues/5635)

This release contained no user-facing changes.

Dependency Bumps

• solo-io/k8s-utils has been upgraded to v0.0.12.

New Features

• Adding Grpc extauth configuration, to be able to set the Authority header. (https://github.com/solo-io/gloo/issues/5682)
• Add new HybridGateway Gateway type which wraps HTTP and TCP Gateways, allowing the user to expose multiple HTTP and/or TCP Gateway on a single port Per-request dynamic Gateway selection is determined by Matchers which enable finer control over Envoy FilterChainMatches (https://github.com/solo-io/gloo/issues/5324)

Fixes

• Update all references to v1beta1 packages, to ensure that ingress installation succeeds on Kube 1.22 (https://github.com/solo-io/gloo/issues/5523)

This release contained no user-facing changes.

This release contained no user-facing changes.

Dependency Bumps

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