generated from kubernetes/kubernetes-template-project
-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to defer preemption when using admission checks #1677
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
Comments
alculquicondor
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
Jan 31, 2024
This was referenced Jan 31, 2024
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Apr 30, 2024
/remove-lifecycle stale |
k8s-ci-robot
removed
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
May 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be added:
The ability for an admission check to influence when preemptions happen (anytime vs after the check has passed).
Why is this needed:
It might be useful if an admission check could take a long time to be satisfied, so that preempting early is not very useful.
However, it's unclear whether the usefulness of this feature outweights the complexity of moving the preemption logic outside of the admission loop. Especially as we start thinking of #62 and #998.
Completion requirements:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.
The text was updated successfully, but these errors were encountered: