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
{{ message }}
Repository navigation
Commit 81df1db
Browse filesBrowse the repository at this point in the historyBrowse files
fix(lineage-webhook): fail admission when a SchedulingClass lookup errors
schedulingClassExists treated every lookup error as absence. A timeout
or a 5xx from the apiserver during Pod admission therefore skipped the
injection, and the Pod ran on the default scheduler, outside the
tenant's placement constraint, until it was recreated.
Only NotFound and NoMatch (the SchedulingClass CRD is not installed) now
count as absence. Any other error is returned, the webhook answers 500,
and with failurePolicy Fail the Pod's controller retries the creation.
Assisted-by: LLM
Signed-off-by: Mattia Eleuteri <[email protected]>
0 commit comments