@@ -86,6 +86,7 @@ Tang operator-bundle are:
86
86
- v1.0.1: new GA release candidate. Update Go version (1.16->1.21) and dependencies
87
87
- v1.0.2: new GA release candidate. Fix CVE-2023 -39325
88
88
- v1.0.3: new GA release candidate. Update all mods to latest version
89
+ - v1.0.4: new GA release candidate. Adjust to naming conventions
89
90
90
91
## Installation
91
92
@@ -107,23 +108,23 @@ operator-sdk installation is described in the [Links](#links) section.
107
108
108
109
In order to deploy the latest version of the Tang operator, check latest released
109
110
version in the [ Versions] ( #versions ) section, and install the appropriate version
110
- bundle. For example, in case latest version is ** 1.0.3 ** , the command to execute
111
+ bundle. For example, in case latest version is ** 1.0.4 ** , the command to execute
111
112
will be:
112
113
113
114
``` bash
114
- $ operator-sdk run bundle quay.io/sec-eng-special/tang-operator-bundle:v1.0.3 --index-image=quay.io/operator-framework/opm:v1.23.0
115
- INFO[0008] Successfully created registry pod: quay-io-sec-eng-special-tang-operator-bundle-v1.0.3
115
+ $ operator-sdk run bundle quay.io/sec-eng-special/tang-operator-bundle:v1.0.4 --index-image=quay.io/operator-framework/opm:v1.23.0
116
+ INFO[0008] Successfully created registry pod: quay-io-sec-eng-special-tang-operator-bundle-v1.0.4
116
117
INFO[0009] Created CatalogSource: tang-operator-catalog
117
118
INFO[0009] OperatorGroup " operator-sdk-og" created
118
- INFO[0009] Created Subscription: tang-operator-v1.0.3 -sub
119
- INFO[0011] Approved InstallPlan install-lqf9f for the Subscription: tang-operator-v1.0.3 -sub
119
+ INFO[0009] Created Subscription: tang-operator-v1.0.4 -sub
120
+ INFO[0011] Approved InstallPlan install-lqf9f for the Subscription: tang-operator-v1.0.4 -sub
120
121
INFO[0011] Waiting for ClusterServiceVersion to reach ' Succeeded' phase
121
- INFO[0012] Waiting for ClusterServiceVersion " default/tang-operator.v1.0.3 "
122
- INFO[0018] Found ClusterServiceVersion " default/tang-operator.v1.0.3 " phase: Pending
123
- INFO[0020] Found ClusterServiceVersion " default/tang-operator.v1.0.3 " phase: InstallReady
124
- INFO[0021] Found ClusterServiceVersion " default/tang-operator.v1.0.3 " phase: Installing
125
- INFO[0031] Found ClusterServiceVersion " default/tang-operator.v1.0.3 " phase: Succeeded
126
- INFO[0031] OLM has successfully installed " tang-operator.v1.0.3 "
122
+ INFO[0012] Waiting for ClusterServiceVersion " default/tang-operator.v1.0.4 "
123
+ INFO[0018] Found ClusterServiceVersion " default/tang-operator.v1.0.4 " phase: Pending
124
+ INFO[0020] Found ClusterServiceVersion " default/tang-operator.v1.0.4 " phase: InstallReady
125
+ INFO[0021] Found ClusterServiceVersion " default/tang-operator.v1.0.4 " phase: Installing
126
+ INFO[0031] Found ClusterServiceVersion " default/tang-operator.v1.0.4 " phase: Succeeded
127
+ INFO[0031] OLM has successfully installed " tang-operator.v1.0.4 "
127
128
```
128
129
To install latest multi-arch image, execute:
129
130
``` bash
@@ -139,10 +140,10 @@ your cluster takes long time to deploy. To do so, the option **--timeout** can b
139
140
used (if not used, default time is 2m, which stands for two minutes):
140
141
141
142
``` bash
142
- $ operator-sdk run bundle --timeout 3m quay.io/sec-eng-special/tang-operator-bundle:v1.0.3 --index-image=quay.io/operator-framework/opm:v1.23.0
143
- INFO[0008] Successfully created registry pod: quay-io-sec-eng-special-tang-operator-bundle-v1.0.3
143
+ $ operator-sdk run bundle --timeout 3m quay.io/sec-eng-special/tang-operator-bundle:v1.0.4 --index-image=quay.io/operator-framework/opm:v1.23.0
144
+ INFO[0008] Successfully created registry pod: quay-io-sec-eng-special-tang-operator-bundle-v1.0.4
144
145
...
145
- INFO[0031] OLM has successfully installed " tang-operator.v1.0.3 "
146
+ INFO[0031] OLM has successfully installed " tang-operator.v1.0.4 "
146
147
```
147
148
148
149
Additionally, correct Tang operator installation can be observed if an output like
@@ -152,7 +153,7 @@ the following is observed when prompting for installed pods:
152
153
$ oc get pods
153
154
NAME READY STATUS RESTARTS AGE
154
155
dbbd1837106ec169542546e7ad251b95d27c3542eb0409c1e 0/1 Completed 0 82s
155
- quay-io-tang-operator-bundle-v1.0.3 1/1 Running 0 90s
156
+ quay-io-tang-operator-bundle-v1.0.4 1/1 Running 0 90s
156
157
tang-operator-controller-manager-5c9488d8dd-mgmsf 2/2 Running 0 52s
157
158
```
158
159
@@ -199,19 +200,19 @@ to be released, it is recommended to increase version appropriately.
199
200
In this case, same version is used. Last released version can be observed in
200
201
[ Versions] ( #versions ) section.
201
202
202
- To summarize, taking into account that the last released version is ** v1.0.3 ** ,
203
+ To summarize, taking into account that the last released version is ** v1.0.4 ** ,
203
204
compilation can be done with next command:
204
205
205
206
``` bash
206
- $ make docker-build docker-push IMG=" quay.io/sec-eng-special/tang-operator:v1.0.3 "
207
+ $ make docker-build docker-push IMG=" quay.io/sec-eng-special/tang-operator:v1.0.4 "
207
208
...
208
209
Successfully built 4a88ba8e6426
209
- Successfully tagged sec-eng-special/tang-operator:v1.0.3
210
- docker push sec-eng-special/tang-operator:v1.0.3
210
+ Successfully tagged sec-eng-special/tang-operator:v1.0.4
211
+ docker push sec-eng-special/tang-operator:v1.0.4
211
212
The push refers to repository [quay.io/sec-eng-special/tang-operator]
212
213
79109912085a: Pushed
213
214
417cb9b79ade: Layer already exists
214
- v1.0.3 : digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
215
+ v1.0.4 : digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
215
216
```
216
217
217
218
In case a new release is planned to be done, the steps to follow will be:
@@ -227,15 +228,15 @@ index 9a41c6a..db12a82 100644
227
228
@@ -3,7 +3,7 @@
228
229
# To re-generate a bundle for another specific version without changing the
229
230
# standard setup, you can:
230
- # - use the VERSION as arg of the bundle target (e.g make bundle VERSION=1.0.3 )
231
- # - use environment variables to overwrite this value (e.g export VERSION=1.0.3 )
231
+ # - use the VERSION as arg of the bundle target (e.g make bundle VERSION=1.0.4 )
232
+ # - use environment variables to overwrite this value (e.g export VERSION=1.0.4 )
232
233
-VERSION ? = 0.0.27
233
- +VERSION ? = 1.0.3
234
+ +VERSION ? = 1.0.4
234
235
```
235
236
236
237
Apart from previous changes, it is recommended to generate a "latest" tag for tang-operator bundle:
237
238
``` bash
238
- $ docker tag quay.io/sec-eng-special/tang-operator-bundle:v1.0.3 quay.io/sec-eng-special/tang-operator-bundle:latest
239
+ $ docker tag quay.io/sec-eng-special/tang-operator-bundle:v1.0.4 quay.io/sec-eng-special/tang-operator-bundle:latest
239
240
$ docker push quay.io/sec-eng-special/tang-operator-bundle:latest
240
241
```
241
242
@@ -245,14 +246,14 @@ Compile Tang operator code, specifying new version,
245
246
by using ** make docker-build** command:
246
247
247
248
``` bash
248
- $ make docker-build docker-push IMG=" quay.io/sec-eng-special/tang-operator:v1.0.3 "
249
+ $ make docker-build docker-push IMG=" quay.io/sec-eng-special/tang-operator:v1.0.4 "
249
250
...
250
- Successfully tagged sec-eng-special/tang-operator:v1.0.3
251
- docker push sec-eng-special/tang-operator:v1.0.3
251
+ Successfully tagged sec-eng-special/tang-operator:v1.0.4
252
+ docker push sec-eng-special/tang-operator:v1.0.4
252
253
The push refers to repository [quay.io/sec-eng-special/tang-operator]
253
254
9ff8a4099c67: Pushed
254
255
417cb9b79ade: Layer already exists
255
- v1.0.3 : digest: sha256:01620ab19faae54fb382a2ff285f589cf0bde6e168f14f07 size: 739
256
+ v1.0.4 : digest: sha256:01620ab19faae54fb382a2ff285f589cf0bde6e168f14f07 size: 739
256
257
```
257
258
258
259
- <ins >Bundle push</ins >:
@@ -262,15 +263,15 @@ the bundle with **make bundle**, specifying appropriate image,
262
263
and push it with ** make bundle-build bundle-push** :
263
264
264
265
``` bash
265
- $ make bundle IMG=" quay.io/sec-eng-special/tang-operator:v1.0.3 "
266
- $ make bundle-build bundle-push BUNDLE_IMG=" quay.io/sec-eng-special/tang-operator-bundle:v1.0.3 "
266
+ $ make bundle IMG=" quay.io/sec-eng-special/tang-operator:v1.0.4 "
267
+ $ make bundle-build bundle-push BUNDLE_IMG=" quay.io/sec-eng-special/tang-operator-bundle:v1.0.4 "
267
268
...
268
- docker push sec-eng-special/tang-operator-bundle:v1.0.3
269
+ docker push sec-eng-special/tang-operator-bundle:v1.0.4
269
270
The push refers to repository [quay.io/sec-eng-special/tang-operator-bundle]
270
271
02e3768cfc56: Pushed
271
272
df0c8060d328: Pushed
272
273
84774958bcf4: Pushed
273
- v1.0.3 : digest: sha256:925c2f844f941db2b53ce45cba9db7ee0be613321da8f0f05d size: 939
274
+ v1.0.4 : digest: sha256:925c2f844f941db2b53ce45cba9db7ee0be613321da8f0f05d size: 939
274
275
make[1]: Leaving directory ' /home/user/RedHat/TASKS/TANG_OPERATOR/tang-operator'
275
276
```
276
277
@@ -310,15 +311,15 @@ In order to cross compile tang-operator, prepend **GOARCH** with required archit
310
311
** make docker-build** :
311
312
312
313
``` bash
313
- $ GOARCH=ppc64le make docker-build docker-push IMG=" quay.io/sec-eng-special/tang-operator:v1.0.3 "
314
+ $ GOARCH=ppc64le make docker-build docker-push IMG=" quay.io/sec-eng-special/tang-operator:v1.0.4 "
314
315
...
315
316
Successfully built 4a88ba8e6426
316
- Successfully tagged sec-eng-special/tang-operator:v1.0.3
317
- docker push sec-eng-special/tang-operator:v1.0.3
317
+ Successfully tagged sec-eng-special/tang-operator:v1.0.4
318
+ docker push sec-eng-special/tang-operator:v1.0.4
318
319
The push refers to repository [quay.io/sec-eng-special/tang-operator]
319
320
79109912085a: Pushed
320
321
417cb9b79ade: Layer already exists
321
- v1.0.3 : digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
322
+ v1.0.4 : digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
322
323
```
323
324
324
325
## Cleanup
@@ -328,9 +329,9 @@ recommended way:
328
329
329
330
``` bash
330
331
$ operator-sdk cleanup tang-operator
331
- INFO[0001] subscription " tang-operator-v1.0.3 -sub" deleted
332
+ INFO[0001] subscription " tang-operator-v1.0.4 -sub" deleted
332
333
INFO[0001] customresourcedefinition " tangservers.daemons.redhat.com" deleted
333
- INFO[0002] clusterserviceversion " tang-operator.v1.0.3 " deleted
334
+ INFO[0002] clusterserviceversion " tang-operator.v1.0.4 " deleted
334
335
INFO[0002] catalogsource " tang-operator-catalog" deleted
335
336
INFO[0002] operatorgroup " operator-sdk-og" deleted
336
337
INFO[0002] Operator " tang-operator" uninstalled
@@ -401,11 +402,11 @@ NOTE: CI/CD is in a continuous "work in progress" state
401
402
402
403
## Scorecard
403
404
404
- Execution of operator-sdk scorecard tests are passing completely in version v1.0.3 .
405
+ Execution of operator-sdk scorecard tests are passing completely in version v1.0.4 .
405
406
In order to execute these tests, run next command:
406
407
407
408
``` bash
408
- $ operator-sdk scorecard -w 60s quay.io/sec-eng-special/tang-operator-bundle:v1.0.3
409
+ $ operator-sdk scorecard -w 60s quay.io/sec-eng-special/tang-operator-bundle:v1.0.4
409
410
...
410
411
Results:
411
412
Name: olm-status-descriptors
0 commit comments