Marked as a pre-release as some of the XDS code still returns v3 resources as v2 resources, which may, in rare cases, cause bugs. The envoy v3 API changes will be reverted in the next release, and completed in a future release.
Helm Changes
- In "gateway" installations of Gloo, enable configuration of the loopback address used for binding the Envoy admin port. This is controlled through the new Helm string value
gatewayProxies.gatewayProxy.loopBackAddress. That same Helm value is also now used to configure the address used for Envoy's readiness probes in a Kubernetes environment. In "ingress" installations of Gloo, Envoy's admin port address is configured using the Helm string valueingressProxy.loopBackAddress. And in "knative" installations, it is configured using the Helm string valuesettings.integrations.knative.proxy.loopBackAddress. (#3114)
Fixes
- Properly suffix all cluster-scoped RBAC resources, including those only relevant to ingress- and knative-mode installations. This ensures that multi-tenant Gloo installations will not experience conflicts on those RBAC resources. (#3103)
- Re add SDS V2 API to SDS container along side new V3 API so that both may run simultaneously while we transition to V3 API in envoy across different components. This change only affects gloo running in MTLS mode. In addition, removing the top level locality field of the Failover API introduce in
v1.4.0-beta15as it does not have any meaningful effect on the underlying implementation. (#3191)