You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/design/milestone-0.0.7/csv-generation.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## Goal
4
4
5
-
The `operator-sdk generate olm-catalog` sub-command should generate a [**Cluster Service Version (CSV)**](olm-csv-definition) customized using information contained in user-defined yaml manifests and Golang source files. Operator developers, *users*, should be able to run `operator-sdk generate olm-catalog` and have their operators' state encapsulated in a CSV; this command should be idempotent and only update the CSV when a yaml manifest or Golang source file is changed. Users should not have to directly interact with a CSV, and should not be required to have in-depth CSV knowledge in order for their operator to interact with [**Operator Lifecycle Manager (OLM)**](olm-description) or publish metadata to the [**Catalog**](catalog-description)
5
+
The `operator-sdk generate olm-catalog` sub-command should generate a [**Cluster Service Version (CSV)**][olm-csv-definition] customized using information contained in user-defined yaml manifests and Golang source files. Operator developers, *users*, should be able to run `operator-sdk generate olm-catalog` and have their operators' state encapsulated in a CSV; this command should be idempotent and only update the CSV when a yaml manifest or Golang source file is changed. Users should not have to directly interact with a CSV, and should not be required to have in-depth CSV knowledge in order for their operator to interact with [**Operator Lifecycle Manager (OLM)**][olm-description] or publish metadata to the [**Catalog**][catalog-description].
6
6
7
7
## Background
8
8
@@ -20,7 +20,7 @@ The `operator-sdk generate olm-catalog` command currently produces a generic CSV
20
20
21
21
1. Create a new CSV, with the same location and naming convention as exists currently, using available data in yaml manifests and Golang source files.
22
22
23
-
1.`renderCSV` will check for an existing CSV in `deploy`. Upon not finding one, a [`ClusterServiceVersion`struct instance](olm-code-csv-struct), defined by the OLM, is created and fields easily derived from operator metadata, such as Kubernetes API `ObjectMeta`, are populated.
23
+
1.`renderCSV` will check for an existing CSV in `deploy`. Upon not finding one, a [`ClusterServiceVersion` instance][olm-code-csv-struct], defined by the OLM, is created and fields easily derived from operator metadata, such as Kubernetes API `ObjectMeta`, are populated.
24
24
1.`renderCSV` will search `deploy` for manifests that contain yaml objects a CSV uses, such as a `Deployment` Kubernetes API resource, and cache found objects in a CSV struct
25
25
1. Once this search completes, every cache instance field populated will be written back to the CSV yaml file. Note that individual yaml objects are overwritten and not the entire file.
26
26
@@ -35,7 +35,7 @@ The `operator-sdk generate olm-catalog` command currently produces a generic CSV
0 commit comments