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