Releases: solo-io/gloo
Releases · solo-io/gloo
v1.15.33
v1.18.0-beta24
Dependency Bumps
- sigs.k8s.io/gateway-api has been upgraded to v1.1.0.
- solo-io/solo-kit has been upgraded to v0.36.1.
Helm Changes
- Adds a new helm value
settings.watchNamespaceSelectors
. This allows users to specify namespaces to watch based on label selectors that can be specified viasettings.watchNamespaceSelectors.matchLabels
for an exact label match andsettings.watchNamespaceSelectors.matchExpressions
for more generic requirements. Thesettings.watchNamespaces
field will override this if specified. (#9274)
New Features
- When using the Kubernetes Gateway API, the provisioned ServiceAccount's labels and annotations are now configurable via the GatewayParameters fields
spec.kube.serviceAccount.extraLabels
andspec.kube.serviceAccount.extraAnnotations
. These values can also be set on the default GatewayParameters during install/upgrade using the Helm valueskubeGateway.gatewayParameters.glooGateway.serviceAccount.extraLabels
andkubeGateway.gatewayParameters.glooGateway.serviceAccount.extraAnnotations
. (solo-io/solo-projects#6846) - Adds a new field
watchNamespaceSelectors
to the settings CR. This allows users to specify namespaces to watch based on label selectors. ThewatchNamespaces
field will override this if specified. (#9274)
Fixes
- Fix a bug that caused discovered Upstreams to not reflect the updated state of parent Services discovered using watchLabels (#8635)
v1.17.11
v1.16.21
v1.15.32
v1.14.32
Fixes
- Fix a bug that caused discovered Upstreams to not reflect the updated state of parent Services discovered using watchLabels (#8635)
- Fix a bug where the service and function names of a discovered gRPC service are not printed in JSON and YAML
output when running glooctl get upstreams (#9743) - Infer the gloo deployment name in cases where the deployment name is not the default
gloo
. The gloo deployment is identified by thegloo=gloo
label. (#9163) - Fix a bug where the service and function names of a discovered gRPC service are not printed when running glooctl get upstreams (#9644)
v1.18.0-beta23
Dependency Bumps
- solo-io/cloud-builders has been upgraded to 0.10.1.
- golang/go has been upgraded to go1.23.1.
- solo-io/go-utils has been upgraded to 0.27.0.
Helm Changes
- Automatically set the GOMAXPROCS environment variable in the gloo and discovery pods when CPU resource limits are set (via the
resources.limits.cpu
deployment helm value). Automatically set the GOMEMLIMIT environment variable in the gloo and discovery pods when memory resource limits are set (via theresources.limits.memory
deployment helm value). These may help limit CPU/memory usage when resource limits are set on the pods. (#10062)
New Features
- Add an API to allow configuring prioritized pools of LLM backends. (solo-io/solo-projects#6957)
- Add an API to allow configuring Weaviate as a backend for semantic caching. (solo-io/solo-projects#6919)
v1.17.10
v1.17.9
Dependency Bumps
- solo-io/solo-kit has been upgraded to v0.35.4.
Fixes
- Adds a new field
watchNamespaceSelectors
to the settings CR. This allows users to specify namespaces to watch based on label selectors. ThewatchNamespaces
field will override this if specified. (#9274) - Adds a new helm value
settings.watchNamespaceSelectors
. This allows users to specify namespaces to watch based on label selectors that can be specified viasettings.watchNamespaceSelectors.matchLabels
for an exact label match andsettings.watchNamespaceSelectors.matchExpressions
for more generic requirements. Thesettings.watchNamespaces
field will override this if specified. (#9274)
v1.18.0-beta22
Dependency Bumps
- solo-io/cloud-builders has been upgraded to 0.10.1.
- golang/go has been upgraded to go1.23.1.
New Features
- Add an API to allow configuring additional labels for AI request stats. (solo-io/solo-projects#6895)
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)