From aa60715e8465b7cc2aa0bd9499bfbe6c0bda76db Mon Sep 17 00:00:00 2001 From: Rishit Dagli Date: Sat, 18 Jun 2022 11:48:00 +0000 Subject: [PATCH] Update Create a Custom Resource Definition Co-authored-by: Antonio Alonso Alarcon --- .../custom-resources/custom-resource-definitions.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) 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 cfe5cb2ad4..4bdc5ca55a 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 @@ -28,11 +28,12 @@ the documentation for that version to see advice that is relevant for your clust ## Create a CustomResourceDefinition When you create a new CustomResourceDefinition (CRD), the Kubernetes API Server -creates a new RESTful resource path for each version you specify. The CRD can be -either namespaced or cluster-scoped, as specified in the CRD's `scope` field. As -with existing built-in objects, deleting a namespace deletes all custom objects -in that namespace. CustomResourceDefinitions themselves are non-namespaced and -are available to all namespaces. +creates a new RESTful resource path for each version you specify. The custom +resource created from a CRD object can be either namespaced or cluster-scoped, +as specified in the CRD's `spec.scope` field. As with existing built-in +objects, deleting a namespace deletes all custom objects in that namespace. +CustomResourceDefinitions themselves are non-namespaced and are available to +all namespaces. For example, if you save the following CustomResourceDefinition to `resourcedefinition.yaml`: