anchor.diff:  // Module included in the following assemblies:
   //
   // * operators/understanding_olm/olm-packaging-format.adoc
  -// * operators/operator_sdk/osdk-managing-bundle-images.adoc
   
   [id="olm-bundle-format_{context}"]
   = Bundle Format
  
positive.code: ├── manifests
  │   ├── etcdcluster.crd.yaml
  │   └── etcdoperator.clusterserviceversion.yaml
  └── metadata
      └── annotations.yaml
      └── dependencies.yaml
  ----
  
  [id="olm-bundle-format-annotations_{context}"]
  == Annotations
  
  A bundle also includes an `annotations.yaml` file in its `metadata/` folder. This file
  defines higher level aggregate data that helps describe the format and package
  information about how the bundle should be added into an index of bundles:
  
  .Example `annotations.yaml`
  [source,yaml]
  
negative.code: Bundle manifests refer to a set of Kubernetes manifests that define the
  deployment and RBAC model of the Operator.
  
  A bundle includes one ClusterServiceVersion (CSV) per directory and typically
  the CRDs that define the owned APIs of the CSV in its `/manifests` directory.
  
  .Example Bundle Format layout
  [source,terminal]
  