The Feature-rich, Kubernetes-native, Next-Generation API Gateway Built on Envoy
APACHE-2.0 License
Bot releases are hidden (Show)
Published by arianaw66 over 4 years ago
Fixes
httpGateway.virtualServiceNamespaces
list, it will now search for virtual services in all the namespaces watched by Gloo. Previously the behavior was to include only virtual services in the same namespace as the gateway, which has proven unintuitive to users. (https://github.com/solo-io/gloo/issues/2156)Published by marcogschmidt over 4 years ago
Helm Changes
New Features
Fixes
httpGateway.virtualServiceNamespaces
list, it will now search for virtual services in all the namespaces watched by Gloo. Previously the behavior was to include only virtual services in the same namespace as the gateway, which has proven unintuitive to users. (https://github.com/solo-io/gloo/issues/2156)Published by marcogschmidt over 4 years ago
Dependency Bumps
Helm Changes
global.glooMtls.enabled
to enable mTLS between Gloo and Envoy (https://github.com/solo-io/gloo/issues/2134). An example of a helm override file that enables MTLS authentication is: glooMtls:
enabled: true
New Features
Fixes
Published by arianaw66 over 4 years ago
Fixes
Published by kdorosh over 4 years ago
Fixes
disableKubernetesDestinations
settings field as a Helm chart value, which if enabled in a Gloo deployment monitoring a large number of kubernetes services, can drastically reduce Gloo memory usage. (https://github.com/solo-io/gloo/issues/2299)Published by yuval-k over 4 years ago
New Features
RouteTableSelector
that matches multiple route tables, Gloo has no way of determining the order in which to process the route tables; in these cases, to avoid short-circuiting routes (e.g. having a route with a /foo
path prefix matcher before one with /foo/bar
), Gloo currently automatically sorts the routes by descending specificity of their matchers. While this prevents short-circuiting errors, it can lead to undesired behavior in cases where the user wants complete control over the final ordering of their routes. To prevent this, we are adding an optional weight
field to the RouteTable
resource. Gloo will now inspect this field to determine the order in which route tables are to be evaluated when a selector
matches multiple ones. This will give the user control over the order in which the routes will appear on the final Proxy
resource. The field is optional; if no value is specified, the weight defaults to 0
(zero). Gloo will process the route tables matched by a selector in ascending order by weight and collect the routes of each route table in the order they are defined. If multiple route tables define the same weight, Gloo will sort the routes which belong to those tables to avoid short-circuiting. In this scenario, Gloo will also alert the user by adding a warning to the status of the parent resource (the one that specifies the RouteTableSelector
). (https://github.com/solo-io/gloo/issues/2233)Fixes
Published by yuval-k over 4 years ago
Dependency Bumps
New Features
name
field to Route object for convenience of naming routes. (https://github.com/solo-io/gloo/issues/2234)disableProxyGarbageCollection
settings field as a Helm chart value. (https://github.com/solo-io/gloo/issues/2323)spec.httpGateway.options.gzip
of the desired Gateway. (https://github.com/solo-io/gloo/issues/2315)Fixes
Published by yuval-k over 4 years ago
Fixes
Published by marcogschmidt over 4 years ago
New Features
disableKubernetesDestinations
settings field as a Helm chart value. (https://github.com/solo-io/gloo/issues/2299)Fixes
glooctl install
command when -f
flag is omitted to no longer error erroneously. (https://github.com/solo-io/gloo/issues/508)pre-upgrade
Helm hooks to avoid failing on upgrades. (https://github.com/solo-io/gloo/issues/2212)ConfigMap
converter. (https://github.com/solo-io/gloo/issues/2277)post-upgrade
Helm hooks. (https://github.com/solo-io/gloo/issues/2212)Published by marcogschmidt over 4 years ago
Dependency Bumps
New Features
Fixes
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. With this change removes the automatic generation feature. Note that the default Settings and Gateway resources in the Helm chart are still marked as Helm hooks. (https://github.com/solo-io/gloo/issues/1828)pre-upgrade
Helm hooks to avoid failing on upgrades. (https://github.com/solo-io/gloo/issues/2212)ConfigMap
converter. (https://github.com/solo-io/gloo/issues/2277)post-upgrade
Helm hooks. (https://github.com/solo-io/gloo/issues/2212)Published by marcogschmidt almost 5 years ago
Downgrading this to a pre-release due to the following regressions:
Dependency Bumps
New Features
glooctl ui
command to open Gloo UI from the command line. (https://github.com/solo-io/gloo/issues/1706)RouteTables
. RouteTables
to delegate to can be selected by either namespaces, labels, or both, using the new RouteTableSelector
field. The routes of all matching RouteTables
will be merged and the resulting route set will be sorted by descending specificity of the matchers on each route, e.g. matchers with longer prefixes will appear first. This feature is meant to replace the virtual service merging feature that we deprecated with the stable v1 release of Gloo. Virtual service merging allowed users to define multiple VirtualServices
for the same domain, which Gloo would then merge into a single VirtualHost
on the Proxy
resource. Although useful to many users, this feature could lead to confusion: the API is not self-documenting with respect to the merging behavior and multiple users could inadvertently step on each other's toes when defining routes for the same domain. As of this release, virtual service merging is not supported anymore; defining two virtual services with overlapping domain sets will result in an error. To be able to define the routes for a given domain on different resources, users can now use the Delegation API. With the new RouteTableSelector
attribute, the Delegation API now enables the same use cases as virtual service merging and has the advantage of surfacing the fact that multiple resources define routes for the same domains to the API. To give a simple example, a Gloo administrator can define a VirtualService
with a single route that delegates all requests for a domain to any RouteTables
that have the domain: example.com
label (namespaces to search can be configured as well); this will allow users to add routes for that domain by creating their own RouteTables
(with a domain: example.com
label) without having to request updates to the parent VirtualService
. (https://github.com/solo-io/gloo/issues/2054)Fixes
glooctl install ingress/knative
to nest helm overrides under "gloo" when a GlooE chart is passed with -f
flag (https://github.com/solo-io/gloo/issues/1999)glooctl install gateway enterprise
to stop nesting helm overrides under "gloo" when a Gloo open-source chart is passed with the -f
flag (https://github.com/solo-io/gloo/issues/2145)Published by marcogschmidt almost 5 years ago
Fixes
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). (https://github.com/solo-io/gloo/issues/2054)Published by marcogschmidt almost 5 years ago
Dependency Bumps
New Features
github.com/solo-io
prefix, as that is no longer assured outside of the GOPATH. (https://github.com/solo-io/gloo/issues/835)Fixes
glooctl get
, we now return a helpful error. (https://github.com/solo-io/gloo/issues/1647)Published by kdorosh almost 5 years ago
New Features
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. 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). (https://github.com/solo-io/gloo/issues/2030)
glooctl install gateway enterprise --version 0.20.6
or glooctl install gateway --version 1.2.1
(https://github.com/solo-io/gloo/issues/1863)Published by kdorosh almost 5 years ago
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
New Features
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 (https://github.com/solo-io/gloo/issues/2048)Published by kdorosh almost 5 years ago
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
Helm Changes
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. (https://github.com/solo-io/gloo/issues/1884)New Features
Fixes
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. (https://github.com/solo-io/gloo/issues/1828)Published by kdorosh almost 5 years ago
This release contained no user-facing changes.
Published by marcogschmidt almost 5 years ago
This release build failed.
New Features
Fixes
glooctl uninstall
now respects all the CLI options when Gloo was not installed via glooctl install
or helm install
. (https://github.com/solo-io/gloo/issues/1938)glooctl install gateway --upgrade
flag, since we have removed the v2 Gateway CRD. (https://github.com/solo-io/gloo/issues/1982)Published by yuval-k almost 5 years ago
Fixes
Published by marcogschmidt almost 5 years ago
This release build failed.
Fixes