Similar to previously closed issue.
This feature request is to run Envoy as a DNS server. A new filter section for DNS can be added, which contains mapping from the dns name to the cluster name. The mapping can be configured statically via the config file or dynamically using xDS API.
Motivation:
We currently have a separate DNS server handling dns requests for our services and with the move to Envoy as our primary routing layer for service-service communication, we would like to move the dns handling as well to a centralized component that is already aware of how to route requests.
Since the filter framework works on a given listener, a UDP filter stack is required for this to work. I see some WIP for a UDP proxy. Would its completion enable this scenario more seamlessly?
@mattklein123
Similar to previously closed issue.
This feature request is to run Envoy as a DNS server. A new filter section for DNS can be added, which contains mapping from the dns name to the cluster name. The mapping can be configured statically via the config file or dynamically using xDS API.
Motivation:
We currently have a separate DNS server handling dns requests for our services and with the move to Envoy as our primary routing layer for service-service communication, we would like to move the dns handling as well to a centralized component that is already aware of how to route requests.
Since the filter framework works on a given listener, a UDP filter stack is required for this to work. I see some WIP for a UDP proxy. Would its completion enable this scenario more seamlessly?
@mattklein123