Make the healthy check end pointer work even if reaches the limitation `maxHttpServerConnections`
Open
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/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!
Contributor guide
Assessment
This issue has not been assessed yet.