There’s a chapter on client-side throttling in the sre book - https://sre.google/sre-book/handling-overload/ https://sre.google/sre-book/handling-overload/ At

There’s a chapter on client-side throttling in the sre book - https://sre.google/sre-book/handling-overload/ https://sre.google/sre-book/handling-overload/ At google we also had to routinely do “backend drains” of particular clusters when we deemed them unhealthy and they had a system to do that quickly at the api/lb layer. At other places I’ve also seen that done with application level flags so you’d do kubectl edit which is obviously less than ideal but worked