You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If any user wants to increase timeoutSeconds in ValidatingWebhookConfiguration and MutatingWebhookConfiguration for the tugger he can’t pass this value in values.yaml file. Currently, your chart is setting default timeoutSeconds i.e. 10 seconds.
The text was updated successfully, but these errors were encountered:
It's true that this isn't configurable in this chart, but I've used ValidatingWebhookConfigurations and MutatingWebhookConfigurations pretty heavily and never needed to change this timeout. I wonder if there's an XY problem here. Why do you need to override this timeout? Tugger should be able to evaluate the rewrite policy very fast. The only case that might have some latency is condition: Exists because it requires a network request, but even that should easily be completed in under 10 seconds.
If any user wants to increase timeoutSeconds in ValidatingWebhookConfiguration and MutatingWebhookConfiguration for the tugger he can’t pass this value in values.yaml file. Currently, your chart is setting default timeoutSeconds i.e. 10 seconds.
The text was updated successfully, but these errors were encountered: