Skip to content

Structured version and feature reporting #5405

@htuch

Description

@htuch

Today, Envoy reports a human readable build version in Node messages when sending xDS requests, and also provides this in the SeverInfo message on the admin console. This is restrictive, since it does not provide detailed information on build details (e.g. was the build FIPS compliant?), version information needs to be parsed out of a string, it's not possible to know which extensions were included, etc.

A full treatment of the existing limitations and a proposal to evolve Envoy's feature/build/version proposal is available at:

https://docs.google.com/document/d/1RlYIzW-R1AtQSJlxAJlIpJEDnLM3a74pCIMrGwAqtNc/edit?usp=sharing

This is an early draft, looking to get feedback and evolve this to meet the community's needs.

CC @mattklein123 @PiotrSikora @mpuncel @snowp @mandarjog

Metadata

Metadata

Assignees

Labels

design proposalNeeds design doc/proposal before implementationhelp wantedNeeds help!

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions