Commit Graph

9 Commits

Author SHA1 Message Date
Kevin Delgado
2d5ceb9b15 drop Enabled() checks for ServerSideFieldValidation feature gate 2023-01-26 14:16:58 +00:00
Kevin Delgado
d983fd8078 Add server-side metadata unknown field validation 2022-07-18 14:55:12 +00:00
Kevin Delgado
7983932800 Exact Matching for Field Validation Tests 2022-03-17 22:08:49 +00:00
Kevin Delgado
a72f24d33c start CRD integration benchmarks 2022-02-18 01:04:51 +00:00
Kevin Delgado
df2768123d
FieldValidation tests for endpoints apiserver and benchmarks for integration tests (#107848)
* wip, working post-strict-yaml

* wip, merge-patch and json-patch tests added

* added SMP tests

* cleanup

* add benchmarks

* more detailed test failure message

* start adding field validation integration benchmarks

* use valid input for benchmarking

* fix remaining integration benchmarks

* benchmarking feedback

* fix endpoints benchmarking

* remove unused vars
2022-02-16 21:19:49 -08:00
Jordan Liggitt
0b90b6ec5e Add field paths to expected unknown/duplicate errors 2021-12-13 09:38:13 -05:00
Jordan Liggitt
d4d34085e4 Clean up field validation test logs 2021-11-21 21:29:06 -05:00
Jordan Liggitt
8fa1c612fd Speed up field validation tests 2021-11-21 21:29:06 -05:00
Kevin Delgado
e50e2bbc88 Server Side Field Validation
Implements server side field validation behind the
`ServerSideFieldValidation` feature gate. With the
feature enabled, any create/update/patch request
with the `fieldValidation` query param set to
"Strict" will error if the object in the request
body have unknown fields. A value of "Warn"
(also the default when the feautre is enabled)
will succeed the request with a warning.

When the feature is disabled (or the query param
has a value of "Ignore"), the request will succeed
as it previously had with no indications of any
unknown or duplicate fields.
2021-11-19 21:24:36 +00:00