envoy: remove usage of deprecated envoy configuration

[LanceEa]

As part of our v3.Y series, we are committed to keeping up-to-date with the Envoy version that is shipped with Emissary-ingress. We have been doing this to ensure we can take advantage of bugfixes, performance enhancements and new features. Most importantly it ensures we are on a supported version that will get security patches from the Envoy Team (this greatly reduces maintainer overhead).

However, between Envoy versions they will deprecate a field and then eventually it will be removed in a future version. This coupled with our faster upgrade cadence means we need to be diligent on removing the usage of these deprecated fields.

This issue is to capture a list of the deprecated behaviors and fields that we need to update:

• [ ] remove usage of runtime flag"envoy.reloadable_features.no_extension_lookup_by_name": false, - https://www.envoyproxy.io/docs/envoy/latest/version_history/v1.22/v1.22.0.html?highlight=no_extension_lookup_by_name
  • [x] envoy.filters.listener.tls_inspector
  • [x] envoy.filters.http.cors
  • [x] envoy.filters.listener.proxy_protocol
  • [x] envoy.filters.http.grpc_http1_bridge
  • [x] envoy.filters.http.grpc_web
  • [x] envoy.filters.http.response_map
  • [ ] envoy.filters.http.lua ?? double check
• [ ] envoy.config.cluster.v3.Cluster.http2_protocol_options - https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/upstreams/http/v3/http_protocol_options.proto#extensions-upstreams-http-v3-httpprotocoloptions
• [ ] envoy.config.cluster.v3.Cluster.common_http_protocol_options - https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/upstreams/http/v3/http_protocol_options.proto#extensions-upstreams-http-v3-httpprotocoloptions
• [ ] envoy.config.route.v3.HeaderMatcher.exact_match -
• [ ] envoy.type.matcher.v3.RegexMatcher
• [ ] envoy.type.matcher.v3.RegexMatcher.GoogleRE2
  • [ ] envoy.type.matcher.v3.RegexMatcher.GoogleRE2.max_program_size
• [ ] Cors settings applied inconfig.route.v3.RouteAction.cors is deprecated in favor of Route.typed_per_filter_config - https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route_components.proto#config-route-v3-routeaction

[zencircle]

Can these added as environment variables on the deployment ? If yes can someone please provide the variables. Thanks

apiVersion: apps/v1
kind: Deployment
spec:
    spec:
      containers:
          env:
            - name: AMBASSADOR_SINGLE_NAMESPACE
              value: 'YES'