Releases: kgateway-dev/kgateway
Releases · kgateway-dev/kgateway
v0.20.12
Dependency Bumps
- solo-io/envoy-gloo has been upgraded to v0.1.18.
- solo-io/solo-kit has been upgraded to v0.11.7.
New Features
- Allow the gateway-proxy pod to optionally receive both init containers to run and extra volumes to define through helm (solo-io#1537)
- This change adds new features to the transformation API. It is now possible to define
Extractor
s which target the request/response body and use the resulting data in templates. You can decide whether to parse the body as JSON or as raw text; in the latter case extraction happens via regular expressions, in the former you will also be able to use all the templating capabilities. These have been augmented with three new template functions:body()
will return the whole request body,context()
will return the base JSON context (allowing for example torange
on a JSON body that is an array), andenv(NAME)
will return the value of an environment variable with the given name. Finally, it is now possible to set Dynamic Metadata using all the available extraction and templating features. You can now use this metadata to include any request/response property you like in the access logs (see theDYNAMIC_METADATA
command operator here). (solo-io#1546)
v0.20.11
New Features
- The default version of GlooE installed by the CLI is now 0.20.6. (solo-io#1386)
v0.20.10
Dependency Bumps
- solo-io/solo-kit has been upgraded to v0.10.5.
New Features
- Add native generated Kubernetes types for Gloo config resources (https://github.com/solo-io/gloo/issues/)
v1.0.0-rc1
Dependency Bumps
- solo-io/solo-kit has been upgraded to v0.11.2.
- solo-io/solo-kit has been upgraded to v0.11.0.
- solo-io/solo-kit has been upgraded to v0.11.5.
- solo-io/reporting-client has been upgraded to v0.1.0.
Breaking Changes
- Make FDS default to whitelist mode (solo-io#1171)
- Flatten prefix rewrite and host rewrite APIs. Move
auto_host_rewrite
from static upstream to route plugins since it's a route-level Envoy config; this fixes confusing behavior where a single static upstream on a route setsauto_host_rewrite
for the entire route. (solo-io#1171) - Add support for multiple matchers on a Gateway/Gloo Route to reduce user duplication in yaml/user code. Also allows users to omit matchers on routes (the
/
prefix matcher will be used) to allow all requests to match the route. (solo-io#1171) - Remove deprecated messages from rbac and jwt. (solo-io#1171)
- Remove deprecated messages from waf. (solo-io#1171)
- Remove the
glooctl --version
command in favor ofglooctl version
(solo-io#1285) - Update glooctl to write using the new strongly-typed API. (solo-io#1171)
New Features
- Allow usage stats collection to be disabled at install time (https://github.com/solo-io/solo-projects/issues/1226)
- Introduce examples project for organizing resources associated with docs and tutorials. (solo-io#1460)
- Add filter level support for matchers in transformation filter. (solo-io/envoy-gloo#34)
Fixes
- Fix generated API field links in docs.solo.io/gloo/latest/. (solo-io#1477)
- Make prefix_rewrite and host_rewrite nullable. (solo-io#1373)
v0.20.9
Dependency Bumps
- solo-io/go-utils has been upgraded to v0.10.20.
- solo-io/solo-kit has been upgraded to v0.11.4.
New Features
- In order to enable routing directly to Kubernetes services (by using
KubernetesServiceDestinations
), Gloo currently scans the cluster for services and creates a special type of in-memory Upstream (via theHybridUpstreamClient
). If the cluster contains a lot of services and the user does not take advantage of this feature, this results in unnecessary overhead. This change adds a newdisable_kubernetes_destinations
attribute to theSettings
resource to allow disabling the feature. (solo-io#1466) - Support matching on headers that do NOT match the specified criteria. (solo-io#1424)
- Add Enterprise API to allow for customization of waf intervention message. (https://github.com/solo-io/solo-projects/issues/1235)
- Allow running the rate limit filter before the auth filters. NOTE that, when this new setting is used, it will result in the loss of the extauth-aware rate limiting feature (ie, different rate limits for authenticated vs unauthenticated users) (solo-io#1445)
Fixes
- Avoid panicking on routes without matchers. (solo-io#1438)
- Fix controller pod crash when settings is missing (solo-io#1498)
- Mute logging of kubernetes health check in gateway (solo-io#1435)
- The Helm chart contained a
Role
/ClusterRole
namedkube-crd-creator
which was unused. This role caused problems to users with limited privileges and effectively prevented them from installing Gloo in namespace-scoped mode. This fix removes thekube-crd-creator
resource from the Helm chart. (solo-io#1491)
v0.20.8
Fixes
- Support setting external traffic policy on gateway proxy services via helm. (solo-io#1410)
v0.20.7
New Features
- Add support for custom authentication. You can now provide your own external authentication/authorization server and configure Gloo to call it on the virtual hosts, routes, and weighted destinations that you want to secure. (solo-io#1396)
- The default version of GlooE installed by the CLI is now 0.20.4. (solo-io#1386)
- Add support for users to provide their own Envoy grpc rate-limit server. (solo-io#1398)
Fixes
- Glooctl no longer registers CRDs when performing read/write operations (solo-io#1380)
- Fix nil pointer when validating nil proxy (solo-io#1369)
v0.20.6
Fixes
- fix nil pointer when validating nil proxy (solo-io#1369)
- check resource hash in validator (prevents validating status updates) (solo-io#1368)
v0.20.5
Fixes
- Some boolean fields on Helm value structs have an
omitempty
json tag. This causes the JSON encoder to considered the whole struct empty in cases where we only the boolean field is set to false and might lead to unexpected behavior. (solo-io#1360) - Fix interface conversion panic on glooctl command to print route table for a virtual service (solo-io#1350)
v0.20.4
Updated to include envoy 1.11.2 and address CVE-2019-15225 and CVE-2019-15226.
Dependency Bumps
- solo-io/envoy-gloo has been upgraded to v0.1.17.