Make the healthy check end pointer work even if reaches the limitation `maxHttpServerConnections`

[poorbarcode]

Search before asking

• [X] I searched in the issues and found nothing similar.

Motivation

maxHttpServerConnections protects the broker when there are many HTTP requests, but it also denies the healthy check call ("/status.html"). Leading the k8s kill the pod even if the broker is fine.

Solution

No response

Alternatives

No response

Anything else?

No response

Are you willing to submit a PR?

• [X] I'm willing to submit a PR!