Skip to content

Commit b0498c8

Browse files
authoredMay 21, 2020
chore: fixed a typo in bundle manifest format
1 parent 18b8ef3 commit b0498c8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed
 

‎docs/design/operator-bundle.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ An `Operator Bundle` is built as a scratch (non-runnable) container image that c
1717

1818
### Bundle Manifest Format
1919

20-
The standard bundle format requires two directories named `manifests` and `metatdata`. The `manifests` directory is where all operator manifests are resided including ClusterServiceVersion (CSV), CustomResourceDefinition (CRD) and other supported Kubernetes types. The `metadata` directory is where operator metadata is located including `annotations.yaml` which contains additional information such as package name, channels and media type. Also, `dependencies.yaml` which contains the operator dependency information can be included in `metadata` directory.
20+
The standard bundle format requires two directories named `manifests` and `metadata`. The `manifests` directory is where all operator manifests are resided including ClusterServiceVersion (CSV), CustomResourceDefinition (CRD) and other supported Kubernetes types. The `metadata` directory is where operator metadata is located including `annotations.yaml` which contains additional information such as package name, channels and media type. Also, `dependencies.yaml` which contains the operator dependency information can be included in `metadata` directory.
2121

2222
Below is the directory layout of an operator bundle inside a bundle image:
2323
```bash

0 commit comments

Comments
 (0)
Please sign in to comment.