Our automation occasionally fails with:

Error from server (InternalError): error when creating "logs/maistra-cr-istio-system.yaml": Internal error occurred: failed calling webhook "smcp.mutation.maistra.io": Post https://maistra-admission-controller.openshift-operators.svc:443/mutate-smcp?timeout=10s: dial tcp 10.129.2.28:11999: connect: connection refused

Repro steps:

1. install istio operator (with 'All namespaces on the cluster' installation mode)
2. create istio-system project
3. wait for istio operator to be installed in istio-system
4. create SMCP

Result:

Occasional failed calling webhook "smcp.mutation.maistra.io"

It seems that the webhook is sometimes not started in time. The steps which reproduce this issue are scripted but valid installation steps so customers might hit it too.

Would it be possible to increase default timeouts so the SMCP installation does not fail when started immediately after operator installation?