Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
docs for field validation GA #39195
docs for field validation GA #39195
Changes from 1 commit
8ea9d24
29e8e40
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
It's good to revise this section, and review the whole document, to frame things differently: validation is server-side, and client-side validation is now deprecated (right?).
Optionally, a client can request either strict validation, or no validation.
Elsewhere in the docs, we should document the warnings that you get from
kubectl
when the input manifest (or partial configuration) either duplicates a field, or refers to a field that the API server doesn't recognise. The key point to bear in mind when revising is the new origin of the warnings. However, the final docs should be timeless and describe the current approach, rather than the change to the new thing.Aside: we ought to have done that wider review when this moved to beta; for graduation to GA, it's essential - there's no later point in the KEP lifecycle to pick up those changes.
If there are big changes needed to docs that another SIG would lead on maintaining, it's OK to instead file and freeze an issue that tracks the changes we need.
Finally, please fix the typo in
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've reworded the introduction and removed references to the "enableability" of the feature-gate throughout (given that server-side validation is now locked to enabled in GA).
Hopefully this reads more timeless, let me know if anything is off.
I've also opened and froze an issue to track the need to update the docs once client side validation is fully removed from kubectl.