kubernetes-sigs
Make sure generated Gateway-API object fields obey kubebuilder max item validation
What would you like to be added: Add a mechanism that considers the kube-builder max item validation on Gateway-API list fields. See this for example.
One option is to validate the constraint, and if it is exceeded - throw an appropriate message. Another option is to add conversion logic that splits objects by these constraints, which will be more challenging.
Why this is needed: To help migrating users who violate those constraints. See https://github.com/kubernetes-sigs/gateway-api/issues/2501 as an example.
@levikobi: This request has been marked as needing help from a contributor.
Guidelines
Please ensure that the issue body includes answers to the following questions:
- Why are we solving this issue?
- To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
- Does this issue have zero to low barrier of entry?
- How can the assignee reach out to you for help?
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
by commenting with the /remove-help command.
In response to this:
/help
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.
