Releases: solo-io/gloo
Releases · solo-io/gloo
v0.19.2
New Features
- Allow using IAM credentials with AWS Upstreams (#680)
- Update enterprise API to have strongly-typed JWT & RBAC config; deprecated opaque extensions config still supported (#1171)
Fixes
- Fix glooctl version output formatting. (#1243)
- The grafana and prometheus pods are now installed to the correct gloo system namespace instead of default (https://github.com/solo-io/solo-projects/issues/1146)
v0.19.1
New Features
- Allow the default gateways to be configurable through helm (#1048)
- Option to install Gloo with a visual dashboard. (#1218)
- Update enterprise API to have strongly-typed WAF config; deprecated opaque extensions WAF config still supported (#1171)
Fixes
- Make sure that glooctl check catches all possible pod conditions (https://github.com/solo-io/solo-projects/issues/1121)
v0.19.0
Marked as pre-release due to helm-chart publish issue.
Dependency Bumps
- solo-io/go-utils has been upgraded to v0.10.8.
Breaking Changes
- Update the external auth APIs to support configuring authentication/authorization on routes and weighted destinations, in addition to virtual hosts. The auth configuration that currently is defined directly on the virtual service/proxy resources (under virtualHostPlugins) will become a top-level solo-kit resource (in the context of Kubernetes this means a new CRD). Resources that need to use a particular auth configuration can now just reference the correspondent new
AuthConfig
resource. The advantages of this change are twofold: besides reducing the duplication of configuration, it guarantees the stability of secured upstreams between auth configuration updates. (#1201)
New Features
- Add plugin to enable envoy health check filter (#1230)
- Allow users to specify the kubernetes cluster name in
glooctl proxy url
andglooctl proxy address
(#1095)
Fixes
v0.18.44
New Features
- Add glooctl debug log command, which prints out all the gloo pod logs. A --zip flag will save them in a tar file (location optionally specified by the --file flag). A --errors-only flag will filter the logs for 'error' level logs. (#997)
Fixes
v0.18.43
New Features
- Ability to specify non-standard kube config from glooctl. (#1094)
- Move rate-limit API from opaque
extensions
to strongly-typedenterprise
tag and deprecate old api (#1171) - add gloo and gateway configuration options to settings (#1145)
- add detailed proxy validation to gloo translator (#1165)
- add proxy validation server to gloo (#1166)
Fixes
v0.18.42
New Features
- Allow container user ids to be dynamically set by the cluster (https://github.com/solo-io/customers/issues/5)
- Modify glooctl version command to output both client and server versions (#722)
- Add support for add route query parameter matching. (#932)
Fixes
- Add back the virtualservice create consul related flags. (#1172)
- If we run glooctl uninstall -all with a nonexistent namespace, still uninstall everything instead of erroring out. (#602)
- For both glooctl add and glooctl create, a --dry-run will output a kube-yaml file unless the --output flag overrides it. (#907)
v0.18.41
v0.18.40
v0.18.39
Fixes
- Fix apiserver intialization restart race condition. (#1149)
- Clarify that UI is read-only, non-enterprise version. (#1146)
- Fix apiserver so that UI can show Envoy details without requiring access to the admin port. (#1125)
- fix issue where the las TLS secret overrides the others when multiple TLS secrets are provided (kubernetes Ingress) (#1151)