-
Notifications
You must be signed in to change notification settings - Fork 276
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
Validate Workload.spec.admission on webhook #328
Comments
/help |
@alculquicondor: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign |
I wonder if we should allow parts of podsets to run first when out of resources, then we can release the resources for the left podsets to run. For podgroup pods, we should have a different set of logic. |
And this can be configured. |
For now, we are going with the assumption that the entire Workload is all-or-nothing. |
What would you like to be added:
The following validations should apply:
Also validate that, once set, the contents of the admission are immutable, except that it can be set to nil.
Why is this needed:
To prevent accidental misuse of this field by administrators.
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: