From ec62317b24c1cda02ef4dd91e9f1eb0daabba3c9 Mon Sep 17 00:00:00 2001 From: Nikhita Raghunath Date: Mon, 11 Jun 2018 23:09:27 +0530 Subject: [PATCH] Update CRD subresources doc for 1.11 (#8918) --- .../extend-api-custom-resource-definitions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions.md b/content/en/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions.md index aefa93f1aa734..1dfa61bdeed2b 100644 --- a/content/en/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions.md +++ b/content/en/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions.md @@ -354,7 +354,7 @@ When the status subresource is enabled, the `/status` subresource for the custom - `PUT` requests to the `/status` subresource only validate the status stanza of the custom resource. - `PUT`/`POST`/`PATCH` requests to the custom resource ignore changes to the status stanza. - Any changes to the spec stanza increments the value at `.metadata.generation`. -- `Properties` and `Required` are the only constructs allowed in the root of the CRD OpenAPI validation schema. +- `properties`, `required` and `description` are the only constructs allowed in the root of the CRD OpenAPI validation schema. #### Scale subresource