@@ -88,6 +88,7 @@ Versions released up to date of the operator and the operator-bundle are:
88
88
- v1.0.12: Fix issues reported by gosec tool
89
89
- v1.0.13: Libraries update, Update Go version (1.22.5 -> 1.23.2)
90
90
- v1.0.14: Rename tang-operator to nbde-tang-server. Use nbde.openshift.io instead of daemons.redhat.com domain
91
+ - v1.1.0: Konflux release candidate
91
92
92
93
## Installation
93
94
@@ -111,7 +112,7 @@ operator-sdk installation is described in the [Links](#links) section.
111
112
112
113
In order to deploy the latest version of the operator, check latest released
113
114
version in the [ Versions] ( #versions ) section, and install the appropriate version
114
- bundle. For example, in case latest version is ** 1.0.14 ** , the command to execute
115
+ bundle. For example, in case latest version is ** 1.1.0 ** , the command to execute
115
116
will be:
116
117
117
118
``` bash
@@ -132,10 +133,10 @@ your cluster takes long time to deploy. To do so, the option **--timeout** can b
132
133
used (if not used, default time is 2m, which stands for two minutes):
133
134
134
135
``` bash
135
- $ operator-sdk run bundle --timeout 3m quay.io/sec-eng-special/nbde-tang-server-bundle:v1.0.14
136
- INFO[0008] Successfully created registry pod: quay-io-sec-eng-special-nbde-tang-server-bundle-v1.0.14
136
+ $ operator-sdk run bundle --timeout 3m quay.io/sec-eng-special/nbde-tang-server-bundle:v1.1.0
137
+ INFO[0008] Successfully created registry pod: quay-io-sec-eng-special-nbde-tang-server-bundle-v1.1.0
137
138
...
138
- INFO[0031] OLM has successfully installed " nbde-tang-server.v1.0.14 "
139
+ INFO[0031] OLM has successfully installed " nbde-tang-server.v1.1.0 "
139
140
```
140
141
141
142
Additionally, correct installation can be observed if an output like
@@ -145,7 +146,7 @@ the following is observed when prompting for installed pods:
145
146
$ oc get pods
146
147
NAME READY STATUS RESTARTS AGE
147
148
dbbd1837106ec169542546e7ad251b95d27c3542eb0409c1e 0/1 Completed 0 82s
148
- quay-io-tang-nbde-tang-server-bundle-v1.0.14 1/1 Running 0 90s
149
+ quay-io-tang-nbde-tang-server-bundle-v1.1.0 1/1 Running 0 90s
149
150
nbde-tang-server-controller-manager-5c9488d8dd-mgmsf 2/2 Running 0 52s
150
151
```
151
152
@@ -195,33 +196,33 @@ to be released, it is recommended to increase version appropriately.
195
196
In this case, same version is used. Last released version can be observed in
196
197
[ Versions] ( #versions ) section.
197
198
198
- To summarize, taking into account that the last released version is ** v1.0.14 ** ,
199
+ To summarize, taking into account that the last released version is ** v1.1.0 ** ,
199
200
compilation can be done with next command:
200
201
201
202
``` bash
202
- $ make docker-build docker-push IMG=" quay.io/sec-eng-special/nbde-tang-server:v1.0.14 "
203
+ $ make docker-build docker-push IMG=" quay.io/sec-eng-special/nbde-tang-server:v1.1.0 "
203
204
...
204
205
Successfully built 4a88ba8e6426
205
- Successfully tagged sec-eng-special/nbde-tang-server:v1.0.14
206
- docker push sec-eng-special/nbde-tang-server:v1.0.14
206
+ Successfully tagged sec-eng-special/nbde-tang-server:v1.1.0
207
+ docker push sec-eng-special/nbde-tang-server:v1.1.0
207
208
The push refers to repository [quay.io/sec-eng-special/nbde-tang-server]
208
- 7910991.0.14a : Pushed
209
+ 7910991.1.0a : Pushed
209
210
417cb9b79ade: Layer already exists
210
- v1.0.14 : digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
211
+ v1.1.0 : digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
211
212
```
212
213
213
214
It is possible to use ` podman ` instead of ` docker ` :
214
215
215
216
``` bash
216
- $ make podman-build podman-push IMG=" quay.io/sec-eng-special/nbde-tang-server:v1.0.14 "
217
+ $ make podman-build podman-push IMG=" quay.io/sec-eng-special/nbde-tang-server:v1.1.0 "
217
218
...
218
219
Successfully built 4a88ba8e6426
219
- Successfully tagged sec-eng-special/nbde-tang-server:v1.0.14
220
- podman push sec-eng-special/nbde-tang-server:v1.0.14
220
+ Successfully tagged sec-eng-special/nbde-tang-server:v1.1.0
221
+ podman push sec-eng-special/nbde-tang-server:v1.1.0
221
222
The push refers to repository [quay.io/sec-eng-special/nbde-tang-server]
222
- 7910991.0.14a : Pushed
223
+ 7910991.1.0a : Pushed
223
224
417cb9b79ade: Layer already exists
224
- v1.0.14 : digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
225
+ v1.1.0 : digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
225
226
```
226
227
227
228
In case a new release is planned to be done, the steps to follow will be:
@@ -237,23 +238,23 @@ index 9a41c6a..db12a82 100644
237
238
@@ -3,7 +3,7 @@
238
239
# To re-generate a bundle for another specific version without changing the
239
240
# standard setup, you can:
240
- # - use the VERSION as arg of the bundle target (e.g. make bundle VERSION=1.0.14 )
241
- # - use environment variables to overwrite this value (e.g. export VERSION=1.0.14 )
241
+ # - use the VERSION as arg of the bundle target (e.g. make bundle VERSION=1.1.0 )
242
+ # - use environment variables to overwrite this value (e.g. export VERSION=1.1.0 )
242
243
-VERSION ? = 1.0.13
243
- +VERSION ? = 1.0.14
244
+ +VERSION ? = 1.1.0
244
245
```
245
246
246
247
Apart from previous changes, it is recommended to generate a "latest" tag for nbde-tang-server bundle:
247
248
248
249
``` bash
249
- $ docker tag quay.io/sec-eng-special/perator-bundle:v1.0.14 quay.io/sec-eng-special/nbde-tang-server-bundle:latest
250
+ $ docker tag quay.io/sec-eng-special/perator-bundle:v1.1.0 quay.io/sec-eng-special/nbde-tang-server-bundle:latest
250
251
$ docker push quay.io/sec-eng-special/nbde-tang-server-bundle:latest
251
252
```
252
253
253
254
In case ` podman ` is being used:
254
255
255
256
``` bash
256
- $ podman tag quay.io/sec-eng-special/nbde-tang-server-bundle:v1.0.14 quay.io/sec-eng-special/nbde-tang-server-bundle:latest
257
+ $ podman tag quay.io/sec-eng-special/nbde-tang-server-bundle:v1.1.0 quay.io/sec-eng-special/nbde-tang-server-bundle:latest
257
258
$ podman push quay.io/sec-eng-special/nbde-tang-server-bundle:latest
258
259
```
259
260
@@ -262,28 +263,28 @@ $ podman push quay.io/sec-eng-special/nbde-tang-server-bundle:latest
262
263
Compile operator code, specifying new version, by using ** make docker-build** command:
263
264
264
265
``` bash
265
- $ make docker-build docker-push IMG=" quay.io/sec-eng-special/nbde-tang-server:v1.0.14 "
266
+ $ make docker-build docker-push IMG=" quay.io/sec-eng-special/nbde-tang-server:v1.1.0 "
266
267
...
267
- Successfully tagged sec-eng-special/nbde-tang-server:v1.0.14
268
- docker push sec-eng-special/nbde-tang-server:v1.0.14
268
+ Successfully tagged sec-eng-special/nbde-tang-server:v1.1.0
269
+ docker push sec-eng-special/nbde-tang-server:v1.1.0
269
270
The push refers to repository [quay.io/sec-eng-special/nbde-tang-server]
270
271
9ff8a4099c67: Pushed
271
272
417cb9b79ade: Layer already exists
272
- v1.0.14 : digest: sha256:01620ab19faae54fb382a2ff285f589cf0bde6e168f14f07 size: 739
273
+ v1.1.0 : digest: sha256:01620ab19faae54fb382a2ff285f589cf0bde6e168f14f07 size: 739
273
274
```
274
275
275
276
And, in case ` podman ` is being used instead of ` docker ` :
276
277
277
278
``` bash
278
- $ make podman-build podman-push IMG=" quay.io/sec-eng-special/nbde-tang-server:v1.0.14 "
279
+ $ make podman-build podman-push IMG=" quay.io/sec-eng-special/nbde-tang-server:v1.1.0 "
279
280
...
280
281
Successfully built 4a88ba8e6426
281
- Successfully tagged sec-eng-special/nbde-tang-server:v1.0.14
282
- podman push sec-eng-special/nbde-tang-server:v1.0.14
282
+ Successfully tagged sec-eng-special/nbde-tang-server:v1.1.0
283
+ podman push sec-eng-special/nbde-tang-server:v1.1.0
283
284
The push refers to repository [quay.io/sec-eng-special/nbde-tang-server]
284
- 7910991.0.14a : Pushed
285
+ 7910991.1.0a : Pushed
285
286
417cb9b79ade: Layer already exists
286
- v1.0.14 : digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
287
+ v1.1.0 : digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
287
288
```
288
289
289
290
- <ins >Bundle push</ins >:
@@ -293,31 +294,31 @@ the bundle with **make bundle**, specifying appropriate image,
293
294
and push it with ** make bundle-build bundle-push** :
294
295
295
296
``` bash
296
- $ make bundle IMG=" quay.io/sec-eng-special/nbde-tang-server:v1.0.14 "
297
- $ make bundle-build bundle-push BUNDLE_IMG=" quay.io/sec-eng-special/nbde-tang-server-bundle:v1.0.14 "
297
+ $ make bundle IMG=" quay.io/sec-eng-special/nbde-tang-server:v1.1.0 "
298
+ $ make bundle-build bundle-push BUNDLE_IMG=" quay.io/sec-eng-special/nbde-tang-server-bundle:v1.1.0 "
298
299
...
299
- docker push sec-eng-special/nbde-tang-server-bundle:v1.0.14
300
+ docker push sec-eng-special/nbde-tang-server-bundle:v1.1.0
300
301
The push refers to repository [quay.io/sec-eng-special/nbde-tang-server-bundle]
301
302
02e3768cfc56: Pushed
302
303
df0c8060d328: Pushed
303
304
84774958bcf4: Pushed
304
- v1.0.14 : digest: sha256:925c2f844f941db2b53ce45cba9db7ee0be613321da8f0f05d size: 939
305
+ v1.1.0 : digest: sha256:925c2f844f941db2b53ce45cba9db7ee0be613321da8f0f05d size: 939
305
306
```
306
307
307
308
In case ` podman ` has been used for container generation, bundle push must be done through ` podman ` .
308
309
In case the operator bundle is required to be pushed, generate the bundle with ** make bundle** ,
309
310
specifying appropriate image, and push it with ** make podman-bundle-build podman-bundle-push** :
310
311
311
312
``` bash
312
- $ make bundle IMG=" quay.io/sec-eng-special/nbde-tang-server:v1.0.14 "
313
- $ make podman-bundle-build podman-bundle-push BUNDLE_IMG=" quay.io/sec-eng-special/nbde-tang-server-bundle:v1.0.14 "
313
+ $ make bundle IMG=" quay.io/sec-eng-special/nbde-tang-server:v1.1.0 "
314
+ $ make podman-bundle-build podman-bundle-push BUNDLE_IMG=" quay.io/sec-eng-special/nbde-tang-server-bundle:v1.1.0 "
314
315
...
315
- podman push sec-eng-special/nbde-tang-server-bundle:v1.0.14
316
+ podman push sec-eng-special/nbde-tang-server-bundle:v1.1.0
316
317
The push refers to repository [quay.io/sec-eng-special/nbde-tang-server-bundle]
317
318
02e3768cfc56: Pushed
318
319
df0c8060d328: Pushed
319
320
84774958bcf4: Pushed
320
- v1.0.14 : digest: sha256:925c2f844f941db2b53ce45cba9db7ee0be613321da8f0f05d size: 939
321
+ v1.1.0 : digest: sha256:925c2f844f941db2b53ce45cba9db7ee0be613321da8f0f05d size: 939
321
322
```
322
323
323
324
** IMPORTANT NOTE** : After bundle generation, next change will appear on the bundle directory:
@@ -358,15 +359,15 @@ In order to cross compile the operator, prepend **GOARCH** with required archite
358
359
** make docker-build** :
359
360
360
361
``` bash
361
- $ GOARCH=ppc64le make docker-build docker-push IMG=" quay.io/sec-eng-special/nbde-tang-server:v1.0.14 "
362
+ $ GOARCH=ppc64le make docker-build docker-push IMG=" quay.io/sec-eng-special/nbde-tang-server:v1.1.0 "
362
363
...
363
364
Successfully built 4a88ba8e6426
364
- Successfully tagged sec-eng-special/nbde-tang-server:v1.0.14
365
- docker push sec-eng-special/nbde-tang-server:v1.0.14
365
+ Successfully tagged sec-eng-special/nbde-tang-server:v1.1.0
366
+ docker push sec-eng-special/nbde-tang-server:v1.1.0
366
367
The push refers to repository [quay.io/sec-eng-special/nbde-tang-server]
367
- 7910991.0.14a : Pushed
368
+ 7910991.1.0a : Pushed
368
369
417cb9b79ade: Layer already exists
369
- v1.0.14 : digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
370
+ v1.1.0 : digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
370
371
```
371
372
Examples of architectures to cross-compile are:
372
373
* ` ppc64le `
@@ -435,7 +436,7 @@ However, scorecard tests can be executed manually. In order to execute these tes
435
436
run next command:
436
437
437
438
``` bash
438
- $ operator-sdk scorecard -w 60s quay.io/sec-eng-special/nbde-tang-server-bundle:v1.0.14
439
+ $ operator-sdk scorecard -w 60s quay.io/sec-eng-special/nbde-tang-server-bundle:v1.1.0
439
440
...
440
441
Results:
441
442
Name: olm-status-descriptors
@@ -462,7 +463,7 @@ Name: olm-bundle-validation
462
463
State: pass
463
464
```
464
465
465
- As it can be observed, execution of operator-sdk scorecard tests are passing successfully in latest released version (v1.0.14 ).
466
+ As it can be observed, execution of operator-sdk scorecard tests are passing successfully in latest released version (v1.1.0 ).
466
467
467
468
## Links
468
469
0 commit comments