Kubernetes Manifest Metadata: Difference between revisions
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
==namespace== | ==namespace== | ||
The <tt>namespace</tt> field specifies the namespace the corresponding object belongs to. When the object is created, it will be created in the specified namespace - which has to exist at the time of the creation. If no namespace field is specified, the default namespace is implied. A missing namespace field is equivalent with a namespace field with the value "default". | The <tt>namespace</tt> field specifies the namespace the corresponding object belongs to. When the object is created, it will be created in the specified namespace - which has to exist at the time of the creation. If no namespace field is specified, the [[Kubernetes_Namespace_Concepts#The_Default_Namespace|default namespace]] is implied. A missing namespace field is equivalent with a namespace field with the value "default". | ||
Revision as of 23:21, 30 August 2019
External
Internal
Overview
Elements
name
The name field specifies the name of the resource. The presence of this field is in general mandatory when creating the resource specified by this manifest, thought in some cases, some resources may allow a client to request the generation of an appropriate name automatically. Once a resource is create, the name cannot be updated.
namespace
The namespace field specifies the namespace the corresponding object belongs to. When the object is created, it will be created in the specified namespace - which has to exist at the time of the creation. If no namespace field is specified, the default namespace is implied. A missing namespace field is equivalent with a namespace field with the value "default".