Kubernetes Manifest Metadata: Difference between revisions
(→name) |
(→labels) |
||
| Line 24: | Line 24: | ||
The <tt>.metadata.labels</tt> field contains a map of string keys and values representing [[Kubernetes Labels and Annotations#Label|labels]]. | The <tt>.metadata.labels</tt> field contains a map of string keys and values representing [[Kubernetes Labels and Annotations#Label|labels]]. | ||
==annotations== | |||
{{External|https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/}} | |||
An unstructured key/value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. | |||
Revision as of 03:49, 27 October 2020
External
Internal
Overview
The manifest metadata section is where things like the resource name and labels are specified.
Elements
name
The .metadata.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. More details:
namespace
The .metadata.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".
labels
The .metadata.labels field contains a map of string keys and values representing labels.
annotations
An unstructured key/value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects.