envoyproxy/envoy

Overload manager action to fail readiness check

Open

#33,168 建立於 2024年3月27日

在 GitHub 查看
 (5 留言) (0 反應) (0 負責人)C++ (5,373 fork)batch import
area/overload_managerenhancementhelp wanted

倉庫指標

Star
 (27,997 star)
PR 合併指標
 (平均合併 8天) (30 天內合併 378 個 PR)

描述

The recommendation in https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge#best-practices-edge for configuring an overload manager looks like so:

  - name: "envoy.overload_actions.shrink_heap"
    triggers:
    - name: "envoy.resource_monitors.fixed_heap"
      threshold:
        value: 0.95
  - name: "envoy.overload_actions.stop_accepting_requests"
    triggers:
    - name: "envoy.resource_monitors.fixed_heap"
      threshold:
        value: 0.98

For folks who are running envoy in a cloud native environment, would it not be better to provide an action that will start failing the healtcheck, so the /ready endpoint starts failing? In this scenario, traffic won't be sent to the pod until the service is healthy again.

貢獻者指南