solo-io/gloo v1.18.0-beta31

on GitHub

Helm Changes

• Expose new Helm values kubeGateway.gatewayParameters.glooGateway.service.extraLabels and kubeGateway.gatewayParameters.glooGateway.service.extraAnnotations to set extra labels and extra annotations on the default GatewayParameters. (https://github.com/solo-io/solo-projects/issues/7090)

New Features

• Add an API to allow configuring CHAT_STREAMING to support Gemini streaming API. (hhttps://github.com/solo-io/solo-projects/issues/7030)
• Add API to enable passthrough auth strategy for AI services. This allows users to pass through the token to the AI service, rather than requiring them to supply a seprate token for the AI service. This can be useful if Identity federation has already been done for the backend in question (https://github.com/solo-io/solo-projects/issues/7115)
• Add API to add moderation as a possible Prompt Guard step. This allows users to add run the user prompt through a moderation service before sending it to the backend LLM. (https://github.com/solo-io/solo-projects/issues/7070)
• The existing Helm values settings.aws.enableServiceAccountCredentials and settings.aws.stsCredentialsRegion are now respected when using Kubernetes Gateway API, as part of supporting AWS Lambda with EKS ServiceAccounts. When settings.aws.enableServiceAccountCredentials is true, a aws_sts_cluster cluster, configured with the STS endpoint specified by settings.aws.stsCredentialsRegion, will automatically be added to dynamically provisioned proxies, so that Envoy can reach AWS to assume the role needed to access Lambdas. (https://github.com/solo-io/solo-projects/issues/6847)

Fixes

• Fix glooctl check so that it only checks Proxies in the write namespace (where all proxies are written), instead of checking in each of the watch namespaces. (#9935)