Skip to content

Commit 1393c49

Browse files
ashishbharthik8s-ci-robot
authored andcommitted
Missing "Manifest" from glossary k8s.io/docs/reference/glossary/ #13546 (#16193)
Added manifest glossary term.
1 parent 406828e commit 1393c49

File tree

2 files changed

+16
-1
lines changed

2 files changed

+16
-1
lines changed

content/en/docs/concepts/cluster-administration/manage-deployment.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ With the above commands, we first create resources under `examples/application/n
106106

107107
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.
108108

109-
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:
109+
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:
110110

111111
```
112112
project/k8s/development
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
title: Manifest
3+
id: manifest
4+
date: 2019-06-28
5+
short_description: >
6+
A serialized specification of one or more Kubernetes API objects.
7+
8+
aka:
9+
tags:
10+
- fundamental
11+
---
12+
Specification of a Kubernetes API object in JSON or YAML format.
13+
14+
<!--more-->
15+
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.

0 commit comments

Comments
 (0)