Stricter server-side validation of JSON entities

[simon3z]

In issue #5850 we mentioned that we may consider a stricter validation of the JSON entities (explicitly failing on unknown fields instead of ignoring them).

[simon3z]

Sorry @brendandburns I just noticed that you closed #5850, do you think that this issue should be closed as well? In #5850 (comment) @bgrant0607 mentioned:

We should probably also do better server-side validation, but need to think through version-skew cases.

so I thought that it was worth to keep track of the possibility for a better server-side validation.

[bgrant0607]

I think it's a reasonable request, though not something we plan to implement soon.

[bgrant0607]

See also discussion in #4855.

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

[bgrant0607]

/remove-lifecycle rotten
/lifecycle frozen

[rikatz]

@bgrant0607 @liggitt I guess this one can be closed, right? AFAIK we already have strict validation on server side for unknown fields

[liggitt]

AFAIK we already have strict validation on server side for unknown fields

no, unknown fields get dropped by the server

[eddiezane]

/remove-sig cli

[kevindelgado]

Fixed by #105916

[kevindelgado]

Can we close this @liggitt? (I don't have permissions to)

[liggitt]

tracked in feature https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/2885-server-side-unknown-field-validation

alpha in 1.23, targeting beta in 1.24