Support drop_overload API#30827
Conversation
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
|
CC @envoyproxy/api-shepherds: Your approval is needed for changes made to |
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
|
/assign @yanavlasov @vishalpowar @adisuissa @KBaichoo |
adisuissa
left a comment
There was a problem hiding this comment.
Thanks for working on this!
Here's a first pass.
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
…overload Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
|
/lgtm api |
KBaichoo
left a comment
There was a problem hiding this comment.
Looks good apart from outstanding comments. Thank you.
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
|
/retest |
1 similar comment
|
/retest |
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
yanavlasov
left a comment
There was a problem hiding this comment.
Looks very good. Thanks. I just have one more suggestion and it is ready to be submitted.
/wait
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
|
/retest |
adisuissa
left a comment
There was a problem hiding this comment.
LGTM, thanks!
/assign-from @envoyproxy/senior-maintainers
|
@envoyproxy/senior-maintainers assignee is @yanavlasov |
|
Kind ping! |
…38408) This is a follow up commit of drop_overload support:#30827. It is observed that in some situations, EDS sends drop_overload ratio as 100% for some clusters do not have healthy endpoints in the cluster. For such cases, it is preferred that the RCD of the local reply set to "unconditional drop overload" to make it a little bit different from the normal "drop overload" case. --------- Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
…38408) This is a follow up commit of drop_overload support:envoyproxy/envoy#30827. It is observed that in some situations, EDS sends drop_overload ratio as 100% for some clusters do not have healthy endpoints in the cluster. For such cases, it is preferred that the RCD of the local reply set to "unconditional drop overload" to make it a little bit different from the normal "drop overload" case. --------- Signed-off-by: Yanjun Xiang <yanjunxiang@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5ff9f03e3af26fad5fd444a4a166c7d8d9b44ffc
…38408) This is a follow up commit of drop_overload support:envoyproxy/envoy#30827. It is observed that in some situations, EDS sends drop_overload ratio as 100% for some clusters do not have healthy endpoints in the cluster. For such cases, it is preferred that the RCD of the local reply set to "unconditional drop overload" to make it a little bit different from the normal "drop overload" case. --------- Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
…nvoyproxy#38408) This is a follow up commit of drop_overload support:envoyproxy#30827. It is observed that in some situations, EDS sends drop_overload ratio as 100% for some clusters do not have healthy endpoints in the cluster. For such cases, it is preferred that the RCD of the local reply set to "unconditional drop overload" to make it a little bit different from the normal "drop overload" case. --------- Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
…nvoyproxy#38408) This is a follow up commit of drop_overload support:envoyproxy#30827. It is observed that in some situations, EDS sends drop_overload ratio as 100% for some clusters do not have healthy endpoints in the cluster. For such cases, it is preferred that the RCD of the local reply set to "unconditional drop overload" to make it a little bit different from the normal "drop overload" case. --------- Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
This PR implement envoy drop_overload support as in:
#3823
For Envoy, it is decided to only support one category at this moment. So, the implementation has size check for drop_overloads configuration.
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]