-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Call createValidation from subresource handlers #72951
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@liggitt what does CREATE operation on subresource pod/eviction mean ? Can subresources be created ? |
This is such a niche requirement of subresources that it seems fairly unlikely that this will be caught in code reviews. Is this required for the common subresources (/status, /spec, /scale) or just resource specific subresources that support create? |
Yes, though from sweeping the code, when createValidation/updateValidation gets called for status and scale subresources, it is passed the object whose status is being updated or which is being scaled (as opposed to the autoscalingv1.Scale object) |
closed in favor of #76910 |
What type of PR is this?
/kind bug
What this PR does / why we need it:
createValidation (which is what calls CREATE admission) was not being called for some custom subresources.
Special notes for your reviewer:
Also moves a couple subresource
createValidation
calls to occur after API validation, matching behavior of standard resources.Does this PR introduce a user-facing change?:
/sig api-machinery
/sig auth
/assign @mikedanese @deads2k
/hold
need to think through the implications of calling admission with the auth[nz] review resources