API Server Rate Limiting Active
warningreliabilityUpdated Nov 10, 2024
API server returning 429 (Too Many Requests) errors indicates clients are being throttled, which can cause controller reconciliation delays and operational failures.
Technologies:
How to detect:
Alert when apiserver_request_total with code=429 rate increases. Cross-reference with apiserver_request_total for codes 500/503 to distinguish rate limiting from server errors.
Recommended action:
Identify high-frequency clients using API server audit logs. Reduce watch/list frequency, implement client-side rate limiting, or increase API server priority and fairness configuration if legitimate load.