-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Ensure conditional validation has knowledge of old and new object #73774
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I need just 1 clarification, other than that looks good.
return fields | ||
} | ||
|
||
// ValidateConditionalPodTemplate validates conditionally valid fields. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could not find Unit tests for ValidateConditionalPodTemplate
any particular reason it does not need one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
both ValidateConditionalPodTemplate
and ValidateConditionalPod
route to validateConditionalPodSpec
, where the validation logic lives, so I just added tests for the latter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, sbezverk 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 |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Moves conditional validation to methods with knowledge of the old and new object, to ensure we never fail an object based on a validation check of data which is already in the existing persisted object.
This ensures that once the SCTP feature is enabled, rollback of one version is safe (API validation-wise).
Which issue(s) this PR fixes:
Finishes #72651
Does this PR introduce a user-facing change?:
/sig api-machinery
/cc @sbezverk