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
The createTaskRun and createCustomRun now uses wait.ExponentialBackoff to retry
the creation of a taskRun or customRun when certain errors occur, specifically
webhook timeouts.
The function isWebhookTimeout checks if an error is a mutating adminssion
webhook timeout, by looking for HTTP 500 and the phrase "timeout" in the error
message.
If a webhook timeout is detected, the backoff loop will retry the creation
up to a configured number of steps, with increasing delay between attempts.
if the error is not a webhook timeout, the function will not retry and will
return the error immediately.
Errors that not webhook timeouts, e.g. HTTP 400 bad request, validation errors,
etc. are not retried and will cause the taskRun creation to fail as expected.
By default, the exponential backoff strategy is disabled. To enable this
feature, set the `enable-wait-exponential-backoff` to `true` in
feature-flags config map.
When enabled, the controller will use an exponential backoff strategy to retry
taskRun and customRun creation if it encounters transient errors such as
admission webhook timeouts.
This improves robustness against temporary webhook issues. If the feature flag
is set to false, the controller will not retry and will fail immediately on
such errors.
Configuration for the backoff parameters (duration, factor, steps, etc) can be
set in the wait-exponential-backoff config map.
Signed-off-by: Priti Desai <[email protected]>
0 commit comments