Emissary-Ingress - v3.4.0

:tada: Emissary Ingress 3.4.0 :tada:

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.4.0/CHANGELOG.md
Get started with Emissary on Kubernetes - https://www.getambassador.io/user-guide/getting-started

• Feature: Support for the getambassador.io/v1 apiVersion has been re-introduced, in order to
  facilitate smoother migrations from Emissary-ingress 1.y. Previously, in order to make migrations
  possible, an "unserved" v1 version was declared to Kubernetes, but was unsupported by
  Emissary-ingress. That unserved v1 could cause an excess of errors to be logged by the
  Kubernetes Nodes (regardless of whether the installation was migrated from 1.y or was a fresh 2.y
  install); fully supporting v1 again should resolve these errors.

• Feature: It is now possible to configure active healhchecking for upstreams within a Mapping. If
  the upstream fails its configured health check then Envoy will mark the upstream as unhealthy and
  no longer send traffic to that upstream. Single pods within a group may can be marked as
  unhealthy. The healthy pods will continue to receive traffic normally while the unhealthy pods
  will not receive any traffic until they recover by passing the health check.

• Feature: The healthcheck server's bind address, bind port and IP family can now be configured
  using environment variables:

• AMBASSADOR_HEALTHCHECK_BIND_ADDRESS: The address to bind the
  healthcheck server to.
• AMBASSADOR_HEALTHCHECK_BIND_PORT: The port to bind the healthcheck
  server to.

• AMBASSADOR_HEALTHCHECK_IP_FAMILY: The IP family to use for the healthcheck
  server.
  This allows the healthcheck server to be configured to use IPv6-only k8s environments.
  (Thanks to Dmitry Golushko!).

• Feature: This upgrades Emissary-ingress to be built on Envoy v1.24.1. One notable change is that
  the team at LightStep and Envoy Maintainers have decided to no longer support the native
  LightStep tracing driver in favor of using the Open Telemetry driver. The code for LightStep
  driver has been completely removed from Envoy code base so Emissary-ingress will no longer
  support it either.
  The recommended upgrade path is to leverage a supported Tracing driver such as
  Zipkin and use the Open Telemetry Collector to
  collect and forward Observabity data to LightStep.