Update docs once client-side validation is removed from kubectl

[kevindelgado]

Server Side Field Validation is on by default starting in Kubernetes 1.25, but still disableable behind a feature-gate in kubernetes 1.25 and 1.26.

When a kubectl of version 1.25+ connects to an API server of 1.26- that has ServerSideFieldValidation disabled, it will fall back on client-side validation.

Once kubectl no longer supports connecting to APIServers 1.26- it will no longer fall back on client-side validation, and client-side validation can be removed entirely from kubectl. Once this occurs, we must update the documentation to remove the notice that kubectl will fall back to client-side validation

[kevindelgado]

/sig cli

[kevindelgado]

/sig api-machinery

[kevindelgado]

/lifecycle frozen

[Shubham82]

/triage accepted

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[Shubham82]

closing this issue, as it was resolved by PR #39715
/close

[k8s-ci-robot]

@Shubham82: Closing this issue.

In response to this:

closing this issue, as it was resolved by PR #39715
/close

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.