v1.2.15

Fixes

• Fix error (and repetitive logging) when Gateway Notification Channel is closed. This issue can happen when network communication between tthe Gloo and Gateway pods is interrupted. (solo-io#2070)
• Wire in grpc web into gloo. (solo-io#555)
• Update the delegation API to support delegating to multiple route tables. Route tables to delegate to can be selected by either namespaces, labels, or both, using the new RouteTableSelector field. The routes of all matching route tables will be merged and the resulting route set will be sorted by descending specificity of the matchers on each route, i.e. matchers with longer prefixes will appear first (delegated routes can only have prefix matchers). (solo-io#2054)

v1.3.1

Dependency Bumps

• solo-io/solo-kit has been upgraded to v0.12.1.

New Features

• Make Gloo fully compatible with go.mod, so that it can be run outside of the GOPATH. As a result of this all of the proto import paths needed to be stripped of the github.com/solo-io prefix, as that is no longer assured outside of the GOPATH. (solo-io#835)

Fixes

• Wire in grpc web into gloo. (solo-io#555)
• undo change to /docs/.gitignore which was failing to commit new generated docs, therefore producing broken links (solo-io#2077)
• If we are searching for resources (e.g. upstreams) in a nonexistent namespace during glooctl get, we now return a helpful error. (solo-io#1647)

v1.3.0

New Features

• Add a new auth_endpoint_query_params field to the AuthConfig CRD. When using the Gloo Enterprise OAuth feature, this allows you to append additional query parameters to the request that Gloo sends to the OIDC authorization endpoint to initiate the authorization code flow. This can be useful to integrate Gloo with some identity providers that require custom parameters to be sent to the authorization endpoint.
  The new field is a map, where each key-value pair will result in an additional query parameter:

  name: google-oidc
  namespace: gloo-system
spec:
  configs:
  - oauth:
      app_url: http://localhost:8080
      callback_path: /callback
      client_id: $CLIENT_ID
      client_secret_ref:
        name: google
        namespace: gloo-system
      issuer_url: https://accounts.google.com
      auth_endpoint_query_params:
        key1 : value1
        key2 : value2

We also added a new --auth-endpoint-query-params flag to the glooctl create authconfig command; the flag takes in a comma-separated list of key value pairs (e.g. a=b,c=d). (solo-io#2030)

• Allow users to specify which release version to install via glooctl with: glooctl install gateway enterprise --version 0.20.6 or glooctl install gateway --version 1.2.1 (solo-io#1863)

v1.2.14

Marked as a pre-release as it tracks the 1.3.x branch instead of the 1.2.x branch, and has some new features. 1.2.15 will be a patch release for any fixes since 1.2.12 (the v1.2.x branch)

Dependency Bumps

• solo-io/go-utils has been upgraded to v0.11.7.

New Features

• Support Manual configuration of SSL for Knative Services. Using the annotations gloo.networking.knative.dev/ssl.sni_domains and gloo.networking.knative.dev/ssl.secret_name, users can manually configure Gloo to serve TLS for their Knative Services (solo-io#2048)

v1.2.13

This release build failed. (Helm charts failed to publish for this version)

Marked as a pre-release as it tracks the 1.3.x branch instead of the 1.2.x branch, and has some new features. 1.2.15 will be a patch release for any fixes since 1.2.12 (the v1.2.x branch)

Dependency Bumps

• solo-io/go-utils has been upgraded to v0.11.5.

Helm Changes

• Ensure that all stats server settings are consistent across open source and enterprise Gloo by moving the enabled logic into a global helper template. This change introduces a global value that all deployments will use as their default stats server settings: global.glooStats.enabled. This value can be overridden by an individual deployment by setting a field on that deployment. For example, to disable stats on discovery, you can do discovery.deployment.stats.enabled=false. Note that this change has converted the stats field on our deployment objects from a boolean to an object with an enabled boolean field inside of it. (solo-io#1884)

New Features

• Generate hash functions to improve CPU performance (solo-io#1711)
• Reduce permissions needed to run glooctl in cluster by removing cross-namespace calls from install command. (solo-io#1765)
• Add support for multiple envoy wasm filters, as well as specifying placement of said filters within the chain. (solo-io#1956)
• Support Knative Ingress Class Annotations. If env var REQUIRE_INGRESS_CLASS=true on the Knative Ingress Controller, only ingresses with the annotation 'networking.knative.dev/ingress.class=gloo.ingress.networking.knative.dev' will be processed. Set Helm value Values.settings.integrations.knative.requireIngressClass=true to enable with Helm. (solo-io#2040)

Fixes

• Don't error on install if gloo installation namespace already exists. (solo-io#1988)
• Settings and Gateway resources currently get automatically created when the gloo and gateway pods (respectively) start up. This creates a race condition with our installation that we currently solve by creating our default Settings and Gateways as Helm Hook resources, which means that they are not managed as a part of the Helm release lifecycle. This is fixed by no longer creating those resources if they do not exist when the pods start up. (solo-io#1828)

v1.2.12

This release contained no user-facing changes.

v1.2.11

This release build failed.

New Features

• Adds the ability to configure WebSocket upgrades on the HTTP Connection Manager and/or as part of a route's options. (solo-io#1132)

Fixes

• glooctl uninstall now respects all the CLI options when Gloo was not installed via glooctl install or helm install. (solo-io#1938)
• Don't attempt to reach the knative api server if the user is doing a dry-run installation. (solo-io#1951)
• Remove glooctl install gateway --upgrade flag, since we have removed the v2 Gateway CRD. (solo-io#1982)
• Make the code around upgrade configs more defensive (solo-io#1979)

v1.2.10

Fixes

• glooctl assumed a kube-based environment when checking for a client/Server version mismtach. When using Consul, this caused a delay in the glooctl command while the connection to kubernetes timed out and a kubernetes error message. The version check for non-kubernetes environments is now disabled. (solo-io#1893)

v1.2.9

This release build failed.

Fixes

• Bump envoy-wasm to resolve issue for loading non-empty config for remote WASM extensions. (solo-io#1919)
• Add CRD resources back to the manifest files that are published as part of a Gloo release. (solo-io#1877)

v1.2.8

New Features

• Add preserve_external_request_id hcm setting (solo-io#1875)
• Gloo now allows updating headers for direct responses. This includes the ability to copy request headers to the direct response via the %REQ(header-name)% format specifier. See here for more information. (solo-io#1912)

Fixes

• The Gateway controller now resyncs Proxy resources when Gloo sends a notification that an event occurred. This allows the Gateway to re-process its resources when a secondary resource such as a proxy or an upstream is modified. (solo-io#1812)