gloo

Dependency Bumps

• golang.org/x/net has been upgraded to v0.0.0-20220906165146-f3363e06e74c.

Fixes

• Updates the default gloo liveness probe (disabled by default) to use a new http server that always returns http 200 "ok". The old probe would wait for xds before signalling health, which in large environments could lag while EDS is warming. This could, in rare cases, cause the gloo pod to needless bounce while it was warming. (https://github.com/solo-io/gloo/issues/7197)
• When a reference to a VirtualHostOption or RouteOption CR is not found, apply a warning on the parent resource, where we previously applied an error. This follows the delegation pattern established by RouteTables, and ensures that resources can be applied asynchronously. (https://github.com/solo-io/gloo/issues/2484)
• Adds the new MaxStreamDuration field to RouteOptions to correspond to envoys config.route.v3.RouteAction.MaxStreamDuration (https://github.com/solo-io/gloo/issues/6943)
• Update Gateway logic for multiple filter chains due to multiple SSL configurations (https://github.com/solo-io/gloo/issues/7155)

New Features

• Adds the new MaxStreamDuration field to RouteOptions to correspond to envoys config.route.v3.RouteAction.MaxStreamDuration (https://github.com/solo-io/gloo/issues/6943)

Fixes

• Updates the default gloo liveness probe (disabled by default) to use a new http server that always returns http 200 "ok". The old probe would wait for xds before signalling health, which in large environments could lag while EDS is warming. This could, in rare cases, cause the gloo pod to needless bounce while it was warming. (https://github.com/solo-io/gloo/issues/7197)
• Post status update rate limit CRs would crash the control plane when they needed a status added.
  This will cause a single cycle of the control plane whenever the crs needed updating. (https://github.com/solo-io/solo-projects/issues/4069)
• Update Gateway logic for multiple filter chains due to multiple SSL configurations (https://github.com/solo-io/gloo/issues/7155)

Dependency Bumps

• golang.org/x/net has been upgraded to v0.0.0-20220906165146-f3363e06e74c.

Fixes

• Adds the new MaxStreamDuration field to RouteOptions to correspond to envoys config.route.v3.RouteAction.MaxStreamDuration (https://github.com/solo-io/gloo/issues/6943)
• Update Gateway logic for multiple filter chains due to multiple SSL configurations (https://github.com/solo-io/gloo/issues/7155)

Dependency Bumps

• golang.org/x/net has been upgraded to v0.0.0-20220906165146-f3363e06e74c.

Dependency Bumps

• golang.org/x/net has been upgraded to v0.0.0-20220906165146-f3363e06e74c.

This release contained no user-facing changes.

Fixes

• Post status update rate limit CRs would crash the control plane when they needed a status added.
  This will cause a single cycle of the control plane whenever the crs needed updating. (https://github.com/solo-io/solo-projects/issues/4069)

New Features

• generalize API for extauth API key auth services such that pluggable storage backends may be used; initially support Kubernetes secrets and Aerospike (https://github.com/solo-io/gloo/issues/3944)

Fixes

• Based on profiling, remove and/or gate places where resources are cloned to speed up translation. (https://github.com/solo-io/gloo/issues/7139)

Fixes

• Fixes issue where gRPC plugin is not reset correctly on every run of the translation loop, causing a slow down in gloo performance and envoy memory spikes. (https://github.com/solo-io/gloo/issues/7165)
• Based on profiling, remove and/or gate places where resources are cloned to speed up translation. (https://github.com/solo-io/gloo/issues/7139)

This release contained no user-facing changes.

Fixes

• Disable istio sidecar injection for Jobs and CronJobs (regardless of global.istioIntegration.disableAutoinjection value) as it causes jobs to hang. (https://github.com/solo-io/gloo/issues/7081)

Fixes

• Disable istio sidecar injection for Jobs and CronJobs (regardless of global.istioIntegration.disableAutoinjection value) as it causes jobs to hang. (https://github.com/solo-io/gloo/issues/7081)

Fixes

• Use kubectl patch rather than read then write pattern to update status on custom resources, which makes gloo a less noisy client to the k8s apiserver. NOTE: Users will need to apply new CRDs with this release to get CRD field defaulting behavior that this fix depends on, or else status updates to brand new resources (i.e. status or status.statuses does not exist) will fail. Even if these status updates fail, data-plane traffic and control-plane updates will be unaffected and work as usual. (https://github.com/solo-io/gloo/issues/7076)

Fixes

• Use kubectl patch rather than read then write pattern to update status on custom resources, which makes gloo a less noisy client to the k8s apiserver. NOTE: Users will need to apply new CRDs with this release to get CRD field defaulting behavior that this fix depends on, or else status updates to brand new resources (i.e. status or status.statuses does not exist) will fail. Even if these status updates fail, data-plane traffic and control-plane updates will be unaffected and work as usual. (https://github.com/solo-io/gloo/issues/7076)

Dependency Bumps

• solo-io/envoy-gloo has been upgraded to v1.23.0-patch7.

Dependency Bumps

• solo-io/envoy-gloo has been upgraded to v1.23.0-patch7.
• solo-io/envoy-gloo has been upgraded to v1.23.0-patch7.

Fixes

• Exit early from the gloo-resource-cleanup job (instead of erroring) if the Gloo Edge CRDs have already been deleted. (https://github.com/solo-io/gloo/issues/7109)
• Return lists of resources even when some have errors in glooctl check to avoid incorrect "missing ref" warnings. (https://github.com/solo-io/gloo/issues/7076)
• Gloo loop a large size pods array in a large size upstreams when using gloo in a large k8s cluster with much pods and upstreams. Using map instead of array will accelerate it. (https://github.com/solo-io/gloo/issues/6899)

Fixes

• Exit early from the gloo-resource-cleanup job (instead of erroring) if the Gloo Edge CRDs have already been deleted. (https://github.com/solo-io/gloo/issues/7109)

Fixes

• Exit early from the gloo-resource-cleanup job (instead of erroring) if the Gloo Edge CRDs have already been deleted. (https://github.com/solo-io/gloo/issues/7109)

Fixes

• Fix for inferring the OSS version from an enterprise install when injecting an SDS sidecar. (https://github.com/solo-io/gloo/issues/6623)
• Return lists of resources even when some have errors in glooctl check to avoid incorrect "missing ref" warnings. (https://github.com/solo-io/gloo/issues/7076)

Fixes

• When a reference to a VirtualHostOption or RouteOption CR is not found, apply a warning on the parent resource, where we previously applied an error. This follows the delegation pattern established by RouteTables, and ensures that resources can be applied asynchronously. (https://github.com/solo-io/gloo/issues/2484)
• Disable istio sidecar injection for Jobs and CronJobs (regardless of global.istioIntegration.disableAutoinjection value) as it causes jobs to hang. (https://github.com/solo-io/gloo/issues/7081)
• Enable to set isolateVirtualHostsBySslConfig parameter in the setting.yaml template by exposing it in the chart.yaml file (https://github.com/solo-io/gloo/issues/6677)
• Fix for inferring the OSS version from an enterprise install when injecting an SDS sidecar. (https://github.com/solo-io/gloo/issues/6623)
• Enable HCM options to support 0-value overrides for Duration and ResourceRef object types (https://github.com/solo-io/gloo/issues/6476)