-
Notifications
You must be signed in to change notification settings - Fork 39.3k
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
ValidateVolumeAttributesClassUpdate also validates new vac object. #122449
Conversation
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
/lgtm |
LGTM label has been added. Git tree hash: c24525f0579c67347f23e51e94a46aa3b8e008ff
|
/assign thockin |
Is there any way that a user out in the world could have somehow updated a saved object into a bad state that would no longer pass this validation? |
No, there's no way for users to do that. we have already validate the meta field of the new obj and other fields are immutable. This PR is just to make sure that we don't have any bad data if we add new mutable fields in the future. |
Thanks! /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: carlory, thockin 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:
ValidateVolumeAttributesClassUpdate also validates new vac object.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
this func has already validate the meta object updates. the parameter and driverName field are immutable. so this changes won't have any effect on user's usage.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: