diff --git a/content/en/docs/concepts/cluster-administration/manage-deployment.md b/content/en/docs/concepts/cluster-administration/manage-deployment.md index 996dfc6096..39e9695062 100644 --- a/content/en/docs/concepts/cluster-administration/manage-deployment.md +++ b/content/en/docs/concepts/cluster-administration/manage-deployment.md @@ -106,7 +106,7 @@ With the above commands, we first create resources under `examples/application/n If you happen to organize your resources across several subdirectories within a particular directory, you can recursively perform the operations on the subdirectories also, by specifying `--recursive` or `-R` alongside the `--filename,-f` flag. -For instance, assume there is a directory `project/k8s/development` that holds all of the manifests needed for the development environment, organized by resource type: +For instance, assume there is a directory `project/k8s/development` that holds all of the {{< glossary_tooltip text="manifests" term_id="manifest" >}} needed for the development environment, organized by resource type: ``` project/k8s/development diff --git a/content/en/docs/reference/glossary/manifest.md b/content/en/docs/reference/glossary/manifest.md new file mode 100644 index 0000000000..b81281ee29 --- /dev/null +++ b/content/en/docs/reference/glossary/manifest.md @@ -0,0 +1,15 @@ +--- +title: Manifest +id: manifest +date: 2019-06-28 +short_description: > + A serialized specification of one or more Kubernetes API objects. + +aka: +tags: +- fundamental +--- + Specification of a Kubernetes API object in JSON or YAML format. + + +A manifest specifies the desired state of an object that Kubernetes will maintain when you apply the manifest. Each configuration file can contain multiple manifests.