What are you trying to do
Currently the only ways to identify misconfiguration are, either carefully checking the ingress logs, or verifying if the proxy is behaving as expected. Sometimes neither one or the other are possible, and depending on what is the misconfiguration, this could leave the exposed service in an insecure way.
What HAProxy Ingress should do or how it should behave differently
Ingress does not have status to alert users about misconfiguration. Patching an annotation should help, but sounds more like a hack-ish than a solution. Events associated with the misconfigured ingress should be a way to notify users. Although a k get ing wouldn't reflect the problem, a k describe ing would do.
What are you trying to do
Currently the only ways to identify misconfiguration are, either carefully checking the ingress logs, or verifying if the proxy is behaving as expected. Sometimes neither one or the other are possible, and depending on what is the misconfiguration, this could leave the exposed service in an insecure way.
What HAProxy Ingress should do or how it should behave differently
Ingress does not have status to alert users about misconfiguration. Patching an annotation should help, but sounds more like a hack-ish than a solution. Events associated with the misconfigured ingress should be a way to notify users. Although a
k get ingwouldn't reflect the problem, ak describe ingwould do.