Helm Changes
- Support for specifying the IP ranges that are allowed to access the load balancer via loadBalancerSourceRanges. Refer to Restrict Access For LoadBalancer Service (#2358)
- Setting nodeport numbers in values.yml did not work due to a typo in the gateway-proxy-service template. Fixed the typo. (#3015)
New Features
- Added additional metrics reporting and examples to the gRPC access logging service. This service is intended to be built upon to handle specific needs for reporting and observability in different advanced use cases. (#2804)
- Adds support for the use of named ports on Kubernetes Ingress objects. (#3050)
- Adds the
customIngressClassvariable to the Gloo Helm Chart, which, when set, will allow overriding the defaultkubernetes.io/ingress.classIngress Class used by Gloo. Use in combination withrequireIngressClassto allow multiple Gloo controllers to partition the Ingress objects within a cluster. (#3047) - Add extauth and ratelimit settings to Gateway httpGateway.options.extauth and httpGateway.options.ratelimit. This takes precedence over the global extauth and ratelimit settings on the Settings object, and allows users to set per-gateway extauth or rate-limit configuration for a set of virtual services. (#2257)
- Expose envoy's core.Http1ProtocolOptions.HeaderKeyFormat in the Gloo API as httpConnectionManager.http_protocol_options.proper_case_header_key_format. By default, all header keys are lower cased. If proper_case_header_key_format is set to true, envoy formats the header by proper casing words: the first character and any character following a special character will be capitalized if it’s an alpha character. For example, “content-type” becomes “Content-Type”, and “foo$b#$are” becomes “Foo$B#$Are”. Note that while this results in most headers following conventional casing, certain headers are not covered. For example, the “TE” header will be formatted as “Te”. (#2940)
Fixes
- Fixes a bug where
glooctl checkwas always reporting that Gloo was out of sync with the rate limiting server when Enterprise Gloo was installed. (#3030) - Fixes a bug where the Gloo Ingress Controller (
ingresspod) would stop processing Ingress updates when a detected Ingressbackendincorrectly referenced a service port. (#3051) - Suppress the usage message for glooctl on error. This makes error messages easier to find. (#2880)