From cd2cb310e8c93ccbf14ae0c844ecaaf63a224aa4 Mon Sep 17 00:00:00 2001 From: Ace Eldeib Date: Sat, 6 Jul 2019 04:18:34 -0700 Subject: [PATCH] nit: fix awkward phrasing around pruning behavior (#15226) --- .../blog/_posts/2019-06-20-Future-of-CRDs-Structural-Schemas.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2019-06-20-Future-of-CRDs-Structural-Schemas.md b/content/en/blog/_posts/2019-06-20-Future-of-CRDs-Structural-Schemas.md index a387b8f1088d0..38f0e39a9e6d9 100644 --- a/content/en/blog/_posts/2019-06-20-Future-of-CRDs-Structural-Schemas.md +++ b/content/en/blog/_posts/2019-06-20-Future-of-CRDs-Structural-Schemas.md @@ -209,7 +209,7 @@ Because we want CRDs to make use of these types as well, we introduce the follow * `x-kubernetes-preserve-unknown-fields: true` — specifies that the pruning algorithm should not prune any field. This can be combined with `x-kubernetes-embedded-resource`. Note that within a nested `properties` or `additionalProperties` OpenAPI schema the pruning starts again. - One can use `x-kubernetes-preserve-unknown-fields: true` at the root of the schema (and inside any `properties`, `additionalProperties`) to get the traditional CRD behaviour that nothing is prune, despite being `spec.preserveUnknownProperties: false` is set. + One can use `x-kubernetes-preserve-unknown-fields: true` at the root of the schema (and inside any `properties`, `additionalProperties`) to get the traditional CRD behaviour that nothing is pruned, despite setting `spec.preserveUnknownProperties: false`. ## Conclusion