-
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
Make nodeaffinity parsing functions return field.Error #96167
Comments
/help |
These constructors raise errors mainly from |
/remove-good-first-issue This is actually not trivial :( |
No, the whole point is to avoid code duplication. We can change all the functions that are called to return field.Error or an aggregation of them. But we have to keep the same function signatures. |
Then I guess this will be a big refactoring task, not just sig/scheduling. |
It's not too big, but indeed beyond scheduling OWNERship /sig api-machinery |
I am handling other funcs in |
The
k8s.io/component-helpers/scheduling/corev1/nodeaffinity
constructors return a parsed version of the input types. While doing that, they detect parsing errors that can be aggregated in higher level validators, such asValidateNodeAffinityArgs
.For a proper implementation, all the returned errors should be of the type field.Error.
/sig scheduling
The text was updated successfully, but these errors were encountered: