From 81014bacede09a322b52058368cc32dbf772e432 Mon Sep 17 00:00:00 2001 From: Marcelo Giles Date: Thu, 11 May 2023 22:32:21 -0700 Subject: [PATCH] Update link --- .../en/docs/concepts/overview/working-with-objects/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/overview/working-with-objects/_index.md b/content/en/docs/concepts/overview/working-with-objects/_index.md index e995f8ddb6a..c80bf860cbc 100644 --- a/content/en/docs/concepts/overview/working-with-objects/_index.md +++ b/content/en/docs/concepts/overview/working-with-objects/_index.md @@ -123,7 +123,7 @@ detail the structure of that `.status` field, and its content for each different ### Server Side Field Validation Starting with Kubernetes v1.25, the API server offers server side -[field validation](https://github.com/kubernetes/website/blob/main/content/en/docs/reference/using-api/api-concepts.md#field-validation) +[field validation](/docs/reference/using-api/api-concepts/#field-validation) that detects unrecognized or duplicate fields in an object. It provides all the functionality of `kubectl --validate` on the server side. The `kubectl` tool uses the `--validate` flag to set the level of field validation. It accepts the values `ignore`, `warn`, and `strict` while also