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 k8s backoff only backoffs when the backoff function returns false, nil.
The usual backoff from OAPI would be:
no backoff on TCP errors,
backoff on some HTTP errors (based on status code).
All CAPOSC OAPI calls use backoff the same way:
response, httpRes, err=oscApiClient.ApiCall()
iferr!=nil {
ifhttpRes!=nil {
// does not trigger backoffreturnfalse, fmt.Errorf("error %w httpRes %s", err, httpRes.Status)
}
// httpRes is currently nil, only TCP errors without http response are leftrequestStr:=fmt.Sprintf("%v", readImageRequest)
ifreconciler.KeepRetryWithError(
requestStr,
httpRes.StatusCode, // triggers a nil pointer exception ...reconciler.ThrottlingErrors) {
// even if there was no nil pointer, will never be called as all http errors have already been handledreturnfalse, nil
}
returnfalse, err
}
returntrue, err
There are two options:
fix backoff
remove backoff
As the cluster-api controller does backoff, backoff on CAPOSC side isn't really necessary.
Removing all backoff code would simplify things and would not change the way CAPOSC works.
The text was updated successfully, but these errors were encountered:
The k8s backoff only backoffs when the backoff function returns
false, nil
.The usual backoff from OAPI would be:
All CAPOSC OAPI calls use backoff the same way:
There are two options:
As the cluster-api controller does backoff, backoff on CAPOSC side isn't really necessary.
Removing all backoff code would simplify things and would not change the way CAPOSC works.
The text was updated successfully, but these errors were encountered: