envoyproxy/envoy

API request: xds async NACK

Open

#9,447 创建于 2019年12月21日

在 GitHub 查看
 (3 评论) (0 反应) (0 负责人)C++ (5,373 fork)batch import
area/xdsenhancementhelp wanted

仓库指标

Star
 (27,997 star)
PR 合并指标
 (平均合并 8天) (30 天内合并 378 个 PR)

描述

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

贡献者指南