<p>envoy container failing while startup with the below error</p>
<pre><code>Configuration does not parse cleanly as v3. v2 configuration is deprecated and will be removed from Envoy at the start of Q1 2021: Unknown field in: {&quot;static_resources&quot;:{&quot;listeners&quot;:[{&quot;address&quot;:{&quot;socket_address&quot;:{&quot;address&quot;:&quot;0.0.0.0&quot;,&quot;port_value&quot;:443}},&quot;filter_chains&quot;:[{&quot;tls_context&quot;:{&quot;common_tls_context&quot;:{&quot;tls_certificates&quot;:[{&quot;private_key&quot;:{&quot;filename&quot;:&quot;/etc/ssl/private.key&quot;},&quot;certificate_chain&quot;:{&quot;filename&quot;:&quot;/etc/ssl/keychain.crt&quot;}}]}},&quot;filters&quot;:[{&quot;typed_config&quot;:{&quot;route_config&quot;:{&quot;name&quot;:&quot;local_route&quot;,&quot;virtual_hosts&quot;:[{&quot;domains&quot;:[&quot;*&quot;],&quot;routes&quot;:[{&quot;match&quot;:{&quot;prefix&quot;:&quot;/&quot;},&quot;route&quot;:{&quot;host_rewrite_literal&quot;:&quot;127.0.0.1&quot;,&quot;cluster&quot;:&quot;service_envoyproxy_io&quot;}}],&quot;name&quot;:&quot;local_service&quot;}]},&quot;@type&quot;:&quot;type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager&quot;,&quot;http_filters&quot;:[{&quot;name&quot;:&quot;envoy.filters.http.router&quot;}],&quot;access_log&quot;:[{&quot;typed_config&quot;:{&quot;@type&quot;:&quot;type.googleapis.com/envoy.extensions.access_loggers.file.v3.FileAccessLog&quot;,&quot;path&quot;:&quot;/dev/stdout&quot;},&quot;name&quot;:&quot;envoy.access_loggers.file&quot;}],&quot;stat_prefix&quot;:&quot;ingress_http&quot;},&quot;name&quot;:&quot;envoy.filters.network.http_connection_manager&quot;}]}],&quot;name&quot;:&quot;listener_0&quot;}],&quot;clusters&quot;:[{&quot;load_assignment&quot;:{&quot;cluster_name&quot;:&quot;service_envoyproxy_io&quot;,&quot;endpoints&quot;:[{&quot;lb_endpoints&quot;:[{&quot;endpoint&quot;:{&quot;address&quot;:{&quot;socket_address&quot;:{&quot;port_value&quot;:8080,&quot;address&quot;:&quot;127.0.0.1&quot;}}}}]}]},&quot;connect_timeout&quot;:&quot;30s&quot;,&quot;name&quot;:&quot;service_envoyproxy_io&quot;,&quot;dns_lookup_family&quot;:&quot;V4_ONLY&quot;,&quot;transport_socket&quot;:{&quot;name&quot;:&quot;envoy.transport_sockets.tls&quot;,&quot;typed_config&quot;:{&quot;@type&quot;:&quot;type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext&quot;,&quot;sni&quot;:&quot;www.envoyproxy.io&quot;}},&quot;type&quot;:&quot;LOGICAL_DNS&quot;}]}}
</code></pre>
<p>Here's my envoy.yaml file</p>
<pre><code>static_resources:

  listeners:
  - name: listener_0
    address:
      socket_address:
        address: 0.0.0.0
        port_value: 443
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          &quot;@type&quot;: type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_http
          access_log:
          - name: envoy.access_loggers.file
            typed_config:
              &quot;@type&quot;: type.googleapis.com/envoy.extensions.access_loggers.file.v3.FileAccessLog
              path: /dev/stdout
          http_filters:
          - name: envoy.filters.http.router
          route_config:
            name: local_route
            virtual_hosts:
            - name: local_service
              domains: [&quot;*&quot;]
              routes:
              - match:
                  prefix: &quot;/&quot;
                route:
                  host_rewrite_literal: 127.0.0.1
                  cluster: service_envoyproxy_io
      tls_context:
        common_tls_context:
          tls_certificates:
            - certificate_chain:
                filename: &quot;/etc/ssl/keychain.crt&quot;
              private_key:
                filename: &quot;/etc/ssl/private.key&quot;

  clusters:
  - name: service_envoyproxy_io
    connect_timeout: 30s
    type: LOGICAL_DNS
    # Comment out the following line to test on v6 networks
    dns_lookup_family: V4_ONLY
    load_assignment:
      cluster_name: service_envoyproxy_io
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: 127.0.0.1
                port_value: 8080
    transport_socket:
      name: envoy.transport_sockets.tls
      typed_config:
        &quot;@type&quot;: type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
        sni: www.envoyproxy.io
</code></pre>
<p>I'm I doing something wrong here?</p>

<p>The error message states that: <code>Configuration does not parse cleanly as v3. v2 configuration is deprecated and will be removed from Envoy at the start of Q1 2021</code>. The v2 xDS APIs are deprecated and will be removed form Envoy in Q1 2021, as per the <a href="https://github.com/envoyproxy/envoy/blob/a52ec8b4146dc7db630cd5372fb714f104e1f740//api/API_VERSIONING.md" rel="nofollow noreferrer">API versioning policy</a>.</p>
<p>According to the official docs you got the following options:</p>
<ol>
<li>In the interim, you can continue to use the v2 API for the transitional period by:</li>
</ol>
<ul>
<li><p>Setting <code>--bootstrap-version</code> 2 on the CLI for a v2 bootstrap file.</p>
</li>
<li><p>Enabling the runtime <em>envoy.reloadable_features.enable_deprecated_v2_api</em> feature. This is implicitly enabled if a v2 <code>--bootstrap-version</code> is set.</p>
</li>
</ul>
<ol start="2">
<li>Or <a href="https://www.envoyproxy.io/docs/envoy/latest/faq/api/envoy_v3#how-do-i-configure-envoy-to-use-the-v3-api" rel="nofollow noreferrer">Configure Envoy to use the v3 API</a></li>
</ol>
<p>More details can be found in the linked docs.</p>
