TooManyRequests(429) should have a non-empty RetryAfter when evicting a pod is not allowed

[mengqiy]

This is a FEATURE REQUEST.

AFAIK, eviciton is first used in kubectl drain in #35483.
If a eviction is not allowed, the caller will get a 429 Too Many Requests, without a RetryAfter advice. See, this
It looks like this:
{
"metadata": {},
"status": "Failure",
"message": "Cannot evict pod as it would violate the pod's disruption budget.",
"code": 429
}

It will be very helpful for kubectl drain and others to have a non-empty RetryAfter field.

cc: @caesarxuchao

[0xmichalis]

/sig apps

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[mengqiy]

/remove-lifecycle rotten
/lifecycle frozen

[mengqiy]

/sig api-machinery