Kubernetes Manifest Metadata: Difference between revisions
| Line 20: | Line 20: | ||
The <tt>namespace</tt> field specifies the Kubernetes [[Kubernetes_Namespace_Concepts#Overview|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". | The <tt>namespace</tt> field specifies the Kubernetes [[Kubernetes_Namespace_Concepts#Overview|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". | ||
==labels== | |||
Revision as of 00:57, 7 September 2019
External
Internal
Overview
The manifest metadata section is where things like the resource name and labels are specified.
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 Kubernetes 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".