-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Field Validation API Concepts #32357
Field Validation API Concepts #32357
Conversation
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
/assign |
/retitle [WIP] placeholder for field validation beta docs |
@kevindelgado I have proposed something in #32592, for the same topic. Would you like review #32592 and see if that covers all changes needed? |
Thanks for the PR. We can can go ahead and merge that. I think the one other piece of documentation we want, is something for the api-concepts page similar to what we have for |
/assign @apelisse |
Technical LGTM |
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.
Remember to remove placeholder.md
from this PR.
55d2b63
to
a760f33
Compare
2fec366
to
1d4accf
Compare
/lgtm |
@kevindelgado: you cannot LGTM your own PR. In response to this:
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. |
feedback/nits addressed, please tag it again @sftim |
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.
One more thought. Assume that some folk don't read the “Setting the field validation level” text because they know it's not enabled for their cluster.
When someone supplies duplicate values and these are eventually accepted, it would be nice to clearly explain which value wins. For JSON, it's the last duplicate - right?
@@ -661,6 +661,76 @@ of single-resource API requests, then aggregates the responses if needed. | |||
By contrast, the Kubernetes API verbs **list** and **watch** allow getting multiple | |||
resources, and **deletecollection** allows deleting multiple resources. | |||
|
|||
## Field validation | |||
|
|||
{{< feature-state for_k8s_version="v1.25" state="beta" >}} |
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.
On reflection, I think this should be for the heading “Setting the field validation level” and not for the 2nd-level field validation heading. Even with the feature gate off, there's some (actually quite a lot) of field validation going on.
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.
moved
{{< feature-state for_k8s_version="v1.25" state="beta" >}} | ||
|
||
By default, the API server drops fields that it does not recognize | ||
from an object it receives. |
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.
from an object it receives. | |
from an input that it receives (for example, the JSON body of a `PUT` request). |
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.
done
By default, the API server drops fields that it does not recognize | ||
from an object it receives. | ||
|
||
The two situations where this will occur are: |
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.
(nit)
The two situations where this will occur are: | |
There are two situations where the API server drops fields that you supplied in an HTTP request. | |
These situations are: |
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.
done
1d4accf
to
4584fd5
Compare
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.
all feedback addressed, ptal @sftim
@@ -661,6 +661,76 @@ of single-resource API requests, then aggregates the responses if needed. | |||
By contrast, the Kubernetes API verbs **list** and **watch** allow getting multiple | |||
resources, and **deletecollection** allows deleting multiple resources. | |||
|
|||
## Field validation | |||
|
|||
{{< feature-state for_k8s_version="v1.25" state="beta" >}} |
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.
moved
{{< feature-state for_k8s_version="v1.25" state="beta" >}} | ||
|
||
By default, the API server drops fields that it does not recognize | ||
from an object it receives. |
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.
done
By default, the API server drops fields that it does not recognize | ||
from an object it receives. | ||
|
||
The two situations where this will occur are: |
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.
done
4584fd5
to
2dc5f25
Compare
Build passes now, ptal @sftim |
/assign @didicodes |
@kevindelgado you set a hold on this PR in #32357 (comment) |
/unhold Not needed anymore. Kevin is out for a while. |
/lgtm |
LGTM label has been added. Git tree hash: b3400bdc27af9d47c37a3535e782c650249c0e63
|
Docs for kubernetes/enhancements#2885