v1.17.14

This release contained no user-facing changes.

v1.17.13

This release contained no user-facing changes.

v1.17.12

Fixes

• Changes to downgrade the level of strictness added in 1.17.8 for TLS secret validation. We still validate several pieces of the cert but also scrub down to usable bits. This means we avoid envoy nacks while allowing more non-useful or functional info in our TLS secrets. This means we are RFC compliant but it may mean that there could exist some cert data in an edge case which we will elide from envoy but previously would be nacked. (https://github.com/solo-io/solo-projects/issues/6772)

v1.16.22

This release contained no user-facing changes.

v1.15.33

This release contained no user-facing changes.

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 via settings.watchNamespaceSelectors.matchLabels for an exact label match and settings.watchNamespaceSelectors.matchExpressions for more generic requirements. The settings.watchNamespaces field will override this if specified. (solo-io#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 and spec.kube.serviceAccount.extraAnnotations. These values can also be set on the default GatewayParameters during install/upgrade using the Helm values kubeGateway.gatewayParameters.glooGateway.serviceAccount.extraLabels and kubeGateway.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. The watchNamespaces field will override this if specified. (solo-io#9274)

Fixes

• Fix a bug that caused discovered Upstreams to not reflect the updated state of parent Services discovered using watchLabels (solo-io#8635)

v1.17.11

Fixes

• Fix a bug that caused discovered Upstreams to not reflect the updated state of parent Services discovered using watchLabels (solo-io#8635)

v1.16.21

Fixes

• Fix a bug that caused discovered Upstreams to not reflect the updated state of parent Services discovered using watchLabels (solo-io#8635)

v1.15.32

Fixes

• Fix a bug that caused discovered Upstreams to not reflect the updated state of parent Services discovered using watchLabels (solo-io#8635)

v1.14.32

Fixes

• Fix a bug that caused discovered Upstreams to not reflect the updated state of parent Services discovered using watchLabels (solo-io#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 (solo-io#9743)
• Infer the gloo deployment name in cases where the deployment name is not the default gloo. The gloo deployment is identified by the gloo=gloo label. (solo-io#9163)
• Fix a bug where the service and function names of a discovered gRPC service are not printed when running glooctl get upstreams (solo-io#9644)