From e81d037e6f1f2e37d5bcd10d2ddcb3c63273c244 Mon Sep 17 00:00:00 2001 From: Tony Le Date: Thu, 12 Sep 2024 12:18:36 -0400 Subject: [PATCH] Update custom-resource-definitions.md --- .../custom-resources/custom-resource-definitions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md b/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md index 3d30ac74a38a4..4f1c9f3428102 100644 --- a/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md +++ b/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md @@ -727,7 +727,7 @@ enable the `CRDValidationRatcheting` use this behavior, which then applies to all CustomResourceDefinitions in your cluster. -Provided you enabled the feature gate, Kubernetes implements _validation racheting_ +Provided you enabled the feature gate, Kubernetes implements _validation ratcheting_ for CustomResourceDefinitions. The API server is willing to accept updates to resources that are not valid after the update, provided that each part of the resource that failed to validate was not changed by the update operation. In other words, any invalid part of the resource