-
Notifications
You must be signed in to change notification settings - Fork 41.5k
feat(DRA): migrate list uniqueness to declarative validation #134496
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
base: master
Are you sure you want to change the base?
Conversation
This change migrates the validation for unique device request names for the DeviceClaim.Requests field to a declarative format. The `+k8s:unique=map` and `+k8s:listMapKey=name` tags have been added to the `Requests` field within the `DeviceClaim` API type. This ensures the generated validation code enforces that all entries in the `requests` slice have a unique `name`.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: yongruilin The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/triage accepted |
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
/assign @thockin |
/retest |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This pull request migrates list uniqueness validation for several fields in the resource.k8s.io API group to a declarative format using validation tags. This aligns with the ongoing effort to make API validation more explicit and self-contained.
The following fields were updated to enforce uniqueness:
Which issue(s) this PR is related to:
Ref:
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: