envoyproxy/envoy

Access log token discovery or validation for xDS

Open

#13.620 aberto em 19 de out. de 2020

Ver no GitHub
 (2 comments) (0 reactions) (0 assignees)C++ (5.373 forks)batch import
area/access_loghelp wanted

Métricas do repositório

Stars
 (27.997 stars)
Métricas de merge de PR
 (Mesclagem média 8d) (378 fundiu PRs em 30d)

Description

Description:

An xDS server may need to deal with multiple Envoy versions (either simultaneously, or over its deployed lifetime). The set of valid access log tokens can vary across Envoy versions. If the xDS server sends a configuration with an invalid log token, that update is rejected with a Not supported field in StreamInfo error message. Other than by parsing the message string in the ErrorDetail, the xDS server doesn't have any way to know that the log token was invalid.

One way to solve this would be for xDS servers to have access to a canonical list of valid log tokens for the Envoy version. Another way could be to use the ErrorDetail.Details field to expose some structured information that the xDS server could use to drop the invalid log token.

Guia do colaborador