whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Create a Custom Resource Definition

Browse Source 
Co-authored-by: Antonio Alonso Alarcon <antonio.al.al@gmail.com>
This commit is contained in:
Rishit Dagli
2022-06-18 11:48:00 +00:00
committed by GitHub
parent 03d464abb1
commit aa60715e84
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md
+6 -5
View File
@@ -28,11 +28,12 @@ the documentation for that version to see advice that is relevant for your clust
## Create a CustomResourceDefinition ## Create a CustomResourceDefinition
When you create a new CustomResourceDefinition (CRD), the Kubernetes API Server 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 creates a new RESTful resource path for each version you specify. The custom
either namespaced or cluster-scoped, as specified in the CRD's `scope` field. As resource created from a CRD object can be either namespaced or cluster-scoped,
with existing built-in objects, deleting a namespace deletes all custom objects as specified in the CRD's `spec.scope` field. As with existing built-in
in that namespace. CustomResourceDefinitions themselves are non-namespaced and objects, deleting a namespace deletes all custom objects in that namespace.
are available to all namespaces. CustomResourceDefinitions themselves are non-namespaced and are available to
all namespaces.
For example, if you save the following CustomResourceDefinition to `resourcedefinition.yaml`: For example, if you save the following CustomResourceDefinition to `resourcedefinition.yaml`: