How to update the readiness/liveness probes timeout values of router deployments managed by the ingress operator

Issue

• Is it possible to update the readiness/liveness probes timeout values for the router container of router deployments that are managed by the ingress operator?
• The 1s timeout can cause unwanted router restarts and loss of application connections. Some users require the ability to set timeout values as large as 5s.
• As an OpenShift administrator with a large cluster and thousands of ingress routes in haproxy.conf, there should be the ability to increase the timeout of the router deployment's liveness probe and readiness probe to allow for all routes to be written to haproxy.conf during pod restart.