solo-io/gloo v1.6.0-beta3

on GitHub

Dependency Bumps

• envoy-gloo/solo-io has been upgraded to v1.17.0-rc1.

Helm Changes

• Removed the global.wasm.enabled HELM value for toggling experimental wasm support. Wasm is now enabled by default. This flag is no longer required as there is no more need for a separate gateway-proxy image since wasm support was merged into upstream envoy. (#3753)
• Addresses minor issue of adding consul configs into helm. (#3698)

New Features

• Use official wasm support from upstream envoy, rather than envoy-wasm fork. (#3753)
• Allow automatic discovery of TLS when using consul services. Requires serveral changes to gloo's helm config to use:
  Set the settings.integrations.consul.useTls flag to true.
  Assign a tag for gloo to recognize as the TLS tag if the default (settings.integrations.consul.tlsTagName=glooUseTls) is insufficient.
  Add the consul root CA for gloo to use at settings.integrations.consul.rootCA
  Once these are setup in gloo, adding the tlsTagName value as a tag to consul services should cause upstreams to automatically
  have TLS when discovered by gloo. As part of this change, the behavior of tag matching between gloo upstreams
  and consul service instances was changed from an exact set match to a subset match.
  Now a match is found if an upstream's instanceTags are a subset of a service instance's tags. (#2544)

Fixes

• Fix the validation API to only return proxies that would be generated by proposed resources if requested. This change means the default behavior matches the kubernetes validation webhook API. By including the top-level value returnProxies=true in the json/yaml request to the API, you can signal the endpoint to return the proxies that would be generated (previously, always returning by default). (#3613)