Emissary Ingress 3.8.0

🎉 Emissary Ingress 3.8.0 🎉

Emissary Ingress is an open source, Kubernetes-native microservices API gateway built on the Envoy Proxy.

Upgrade Emissary - https://www.getambassador.io/reference/upgrading.html
View changelog - https://github.com/emissary-ingress/emissary/blob/v3.8.0/CHANGELOG.md
Get started with Emissary on Kubernetes - https://www.getambassador.io/user-guide/getting-started

• Bugfix: As of v2.2.2, if two mappings were associated with different Hosts through host
  mappingSelector labels but share the same prefix, the labels were not taken into account which
  would cause one Mapping to be correctly routed but the other not.
  This change fixes this issue so
  that Mappings sharing the same prefix but associated with different Hosts will be correctly
  routed. (Canary grouping must take labels into account)

• Bugfix: In previous versions, if multiple Headers/QueryParameters where used in a v3alpha1
  mapping, these values would duplicate and cause all the Headers/QueryParameters to have the same
  value. This is no longer the case and the expected values for unique Headers/QueryParameters will
  apply.
  This issue was only present in v3alpha1 Mappings. For users who may have this issue, please
  be sure to re-apply any v3alpha1 Mappings in order to update the stored v2 Mapping and resolve the
  issue.

• Change: When the Ambassador agent is being used, it will no longer attempt to collect and report
  Envoy metrics. In previous versions, Emissary-ingress would always create an Envoy stats sink for
  the agent as long as the AMBASSADOR_GRPC_METRICS_SINK environmet variable was provided. This
  environment variable was hardcoded on the release manifests and has now been removed and an Envoy
  stats sink for the agent is no longer created.