validatingWebhookTimeoutSeconds might be set too low for larger workloads

The default of "3" for this helm value: "validatingWebhookTimeoutSeconds" might be too short/low for some environments. When deploying applications on top of BigBang, we saw maybe 30% of the time the default of "3" timeout prematurely, causing the helm installation of our application charts to fail outright.

We have increased the value to "15" in the values file that we provide to the BigBang chart, as follows:

gatekeeper:
  values:
    # Increasing from 3 to 15 since this is a fatal failure for our application-level helm installation:
    validatingWebhookTimeoutSeconds: 15

15s might be too long, but it shouldn't need that much time if all is well. If all isn't well, then 15s isn't a big deal to wait to fail.

Please correct me if my thinking is misguided.