@@ -110,10 +110,10 @@ Procedure
110
110
mkdir < catalog_dir>
111
111
` ` `
112
112
113
- 1. Create a Dockerfile that can build a catalog image by running the ` opm generate dockerfile ` command :
113
+ 1. In the same directory level, create a Dockerfile that can build a catalog image:
114
114
115
- ` ` ` sh
116
- opm generate dockerfile < catalog_dir >
115
+ ` ` ` sh
116
+ touch Dockerfile
117
117
` ` `
118
118
119
119
* The Dockerfile must be in the same parent directory as the catalog directory that you created in the previous step:
@@ -125,6 +125,17 @@ Procedure
125
125
└── < catalog_dir> .Dockerfile
126
126
` ` `
127
127
128
+ 1. Make the below changes to your Dockerfile:
129
+
130
+ * Example Dockerfile*
131
+
132
+ ` ` ` sh
133
+ FROM scratch
134
+ ADD < catalog_dir> /configs
135
+ ` ` `
136
+
137
+ > ** Note:** Use the ` FROM scratch` directive to make the size of the image smaller.
138
+
128
139
1. Populate the catalog with the package definition for your Operator by running the ` opm init` command:
129
140
130
141
` ` ` sh
@@ -173,7 +184,7 @@ Procedure
173
184
```json
174
185
{
175
186
"schema": "olm.bundle",
176
- "name": "<operator_name>.<version>",
187
+ "name": "<operator_name>.v <version>",
177
188
"package": "<operator_name>",
178
189
"image": "quay.io/<organization_name>/<repository_name>:<image_tag>",
179
190
"properties": [
@@ -199,16 +210,18 @@ Procedure
199
210
```json
200
211
{
201
212
"schema": "olm.channel",
202
- "name": "<default_channel_name >",
213
+ "name": "<desired_channel_name >",
203
214
"package": "<operator_name>",
204
215
"entries": [
205
216
{
206
- "name": "<operator_name>/<bundle_version >"
217
+ "name": "<operator_name>.v<version >"
207
218
}
208
219
]
209
220
}
210
221
```
211
222
223
+ > **Note:** Some examples for the <desired_channel_name> include `stable`, `fast`, and `preview`.
224
+
212
225
<h3 id="verify-adding-a-plain-bundle-to-fbc">
213
226
Verification
214
227
</h3>
0 commit comments