Update Create a Custom Resource Definition
Co-authored-by: Antonio Alonso Alarcon <antonio.al.al@gmail.com>
This commit is contained in:
parent
03d464abb1
commit
aa60715e84
|
@ -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`:
|
||||
|
||||
|
|
Loading…
Reference in New Issue