Istio-IngressGateway Unhealthy Events when Pod gets Created Initially

During ingress-gateway pod startup, there are always unhealthy events appearing for a few seconds in the controlplane namespace.

There should be a way to configure the initalDelaySeconds for gateways in servicemesh.

[quicklab@upi-0 ~]$ oc get pods | grep -i ingress
istio-ingressgateway-b5d4b99cc-c4wwk 1/1 Running 0 33s
[quicklab@upi-0 ~]$

[quicklab@upi-0 ~]$ oc delete pod istio-ingressgateway-b5d4b99cc-c4wwk
pod "istio-ingressgateway-b5d4b99cc-c4wwk" deleted
[quicklab@upi-0 ~]$

[quicklab@upi-0 ~]$ oc get events | grep -i unhealthy | grep ingress
11s Warning Unhealthy pod/istio-ingressgateway-b5d4b99cc-c4wwk Readiness probe failed: Get "http://10.128.2.32:15021/healthz/ready": dial tcp 10.128.2.32:15021: connect: connection refused
8s Warning Unhealthy pod/istio-ingressgateway-b5d4b99cc-c4wwk Readiness probe failed: Get "http://10.128.2.32:15021/healthz/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
55s Warning Unhealthy pod/istio-ingressgateway-b5d4b99cc-ch6bk Readiness probe failed: Get "http://10.128.2.29:15021/healthz/ready": dial tcp 10.128.2.29:15021: connect: connection refused
17m Warning Unhealthy pod/istio-ingressgateway-b5d4b99cc-pmdxj Readiness probe failed: Get "http://10.131.0.40:15021/healthz/ready": dial tcp 10.131.0.40:15021: connect: connection refused
17m Warning Unhealthy pod/istio-ingressgateway-b5d4b99cc-pmdxj Readiness probe failed: Get "http://10.131.0.40:15021/healthz/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
12s Warning Unhealthy pod/istio-ingressgateway-b5d4b99cc-z5sgk Readiness probe failed: Get "http://10.128.2.33:15021/healthz/ready": dial tcp 10.128.2.33:15021: connect: connection refused
[quicklab@upi-0 ~]$