Illegal map value with envoy v3 about typed_config http connection manager
Yes, its a bit of a pain.There's an online envoy config checker that helps a bit in determining exactly which versions ditch backwards compatability.
You have correctly switched from the legacy config to typed_config data.
However, it looks like you inadvertently included a tab in your latest config (line 15) which causes illegal map value.
You also need to migrate clusters/hosts section to load_assignments like this:
load_assignment: cluster_name: grpc-backend-services endpoints: - lb_endpoints: - endpoint: address: socket_address: address: 127.0.0.1 port_value: 53000There's a good example in the current envoy docs: https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter