API request: xds async NACK
Offen
area/xds
enhancement
help wanted
- Vorherrschende Sprache
- C++
- Sterne
- 28.9k
- Forks
- 5.6k
- Ø Merge
- 1 T. 22 Std.
- Gemergte PRs (30 T.)
- 430
Beschreibung
When envoy receives a listener from management server it has 3 choices
1. accept listener and put it in ready state
2. Reject listener with a NACK
3. Accept config and put listener in a warming state awaiting an async operation.
If the async operation fails for any reason and it was performed against separate management server, the original management server has no way to know what happened.
There should be a way to indicate a NACK after async operations complete.
This happens with SDS, Wasm code fetch via url or fcds.
Related issues:
https://github.com/envoyproxy/envoy/issues/5739
https://github.com/envoyproxy/envoy/issues/7867
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.