Release 1.0.10 version

Resolves: #315

Signed-off-by: Sergio Arroutbi <[email protected]>

.github/workflows/deploy.yaml

@@ -52,5 +52,5 @@ jobs:
       - name: Deploy and Scorecard
         run: |
           sh .github/workflows/scripts/retrieve_and_run_operator_sdk \
-            "v1.33.0" "5m" "quay.io/sec-eng-special/tang-operator-bundle" \
+            "v1.35.0" "5m" "quay.io/sec-eng-special/tang-operator-bundle" \
             "${GITHUB_HEAD_REF}"

Makefile

@@ -3,7 +3,7 @@
 # To re-generate a bundle for another specific version without changing the standard setup, you can:
 # - use the VERSION as arg of the bundle target (e.g make bundle VERSION=0.0.2)
 # - use environment variables to overwrite this value (e.g export VERSION=0.0.2)
-VERSION ?= 1.0.9
+VERSION ?= 1.0.10
 
 # CHANNELS define the bundle channels used in the bundle.
 # Add a new line here if you would like to change its default config. (E.g CHANNELS = "candidate,fast,stable")

README.md

@@ -94,6 +94,7 @@ Tang operator-bundle are:
 -  v1.0.7: GA re-release. Fix channel ("alpha" to "stable")
 -  v1.0.8: ServiceType / ClusterIP configuration through TangServer CR
 -  v1.0.9: Golang dependencies update
+- v1.0.10: Libraries update
 
 ## Installation
 
@@ -117,23 +118,23 @@ operator-sdk installation is described in the [Links](#links) section.
 
 In order to deploy the latest version of the Tang operator, check latest released
 version in the [Versions](#versions) section, and install the appropriate version
-bundle. For example, in case latest version is **1.0.9**, the command to execute
+bundle. For example, in case latest version is **1.0.10**, the command to execute
 will be:
 
 ```bash
-$ operator-sdk run bundle quay.io/sec-eng-special/tang-operator-bundle:v1.0.9
-INFO[0008] Successfully created registry pod: quay-io-sec-eng-special-tang-operator-bundle-v1.0.9
+$ operator-sdk run bundle quay.io/sec-eng-special/tang-operator-bundle:v1.0.10
+INFO[0008] Successfully created registry pod: quay-io-sec-eng-special-tang-operator-bundle-v1.0.10
 INFO[0009] Created CatalogSource: tang-operator-catalog
 INFO[0009] OperatorGroup "operator-sdk-og" created
-INFO[0009] Created Subscription: tang-operator-v1.0.9-sub
-INFO[0011] Approved InstallPlan install-lqf9f for the Subscription: tang-operator-v1.0.9-sub
+INFO[0009] Created Subscription: tang-operator-v1.0.10-sub
+INFO[0011] Approved InstallPlan install-lqf9f for the Subscription: tang-operator-v1.0.10-sub
 INFO[0011] Waiting for ClusterServiceVersion to reach 'Succeeded' phase
-INFO[0012]   Waiting for ClusterServiceVersion "default/tang-operator.v1.0.9"
-INFO[0018]   Found ClusterServiceVersion "default/tang-operator.v1.0.9" phase: Pending
-INFO[0020]   Found ClusterServiceVersion "default/tang-operator.v1.0.9" phase: InstallReady
-INFO[0021]   Found ClusterServiceVersion "default/tang-operator.v1.0.9" phase: Installing
-INFO[0031]   Found ClusterServiceVersion "default/tang-operator.v1.0.9" phase: Succeeded
-INFO[0031] OLM has successfully installed "tang-operator.v1.0.9"
+INFO[0012]   Waiting for ClusterServiceVersion "default/tang-operator.v1.0.10"
+INFO[0018]   Found ClusterServiceVersion "default/tang-operator.v1.0.10" phase: Pending
+INFO[0020]   Found ClusterServiceVersion "default/tang-operator.v1.0.10" phase: InstallReady
+INFO[0021]   Found ClusterServiceVersion "default/tang-operator.v1.0.10" phase: Installing
+INFO[0031]   Found ClusterServiceVersion "default/tang-operator.v1.0.10" phase: Succeeded
+INFO[0031] OLM has successfully installed "tang-operator.v1.0.10"
 ```
 To install latest multi-arch image, execute:
 ```bash
@@ -149,10 +150,10 @@ your cluster takes long time to deploy. To do so, the option **--timeout** can b
 used (if not used, default time is 2m, which stands for two minutes):
 
 ```bash
-$ operator-sdk run bundle --timeout 3m quay.io/sec-eng-special/tang-operator-bundle:v1.0.9
-INFO[0008] Successfully created registry pod: quay-io-sec-eng-special-tang-operator-bundle-v1.0.9
+$ operator-sdk run bundle --timeout 3m quay.io/sec-eng-special/tang-operator-bundle:v1.0.10
+INFO[0008] Successfully created registry pod: quay-io-sec-eng-special-tang-operator-bundle-v1.0.10
 ...
-INFO[0031] OLM has successfully installed "tang-operator.v1.0.9"
+INFO[0031] OLM has successfully installed "tang-operator.v1.0.10"
 ```
 
 Additionally, correct Tang operator installation can be observed if an output like
@@ -162,7 +163,7 @@ the following is observed when prompting for installed pods:
 $ oc get pods
 NAME                                                READY STATUS    RESTARTS AGE
 dbbd1837106ec169542546e7ad251b95d27c3542eb0409c1e   0/1   Completed 0        82s
-quay-io-tang-operator-bundle-v1.0.9                 1/1   Running   0        90s
+quay-io-tang-operator-bundle-v1.0.10                1/1   Running   0        90s
 tang-operator-controller-manager-5c9488d8dd-mgmsf   2/2   Running   0        52s
 ```
 
@@ -212,33 +213,33 @@ to be released, it is recommended to increase version appropriately.
 In this case, same version is used. Last released version can be observed in
 [Versions](#versions) section.
 
-To summarize, taking into account that the last released version is **v1.0.9**,
+To summarize, taking into account that the last released version is **v1.0.10**,
 compilation can be done with next command:
 
 ```bash
-$ make docker-build docker-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.9"
+$ make docker-build docker-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.10"
 ...
 Successfully built 4a88ba8e6426
-Successfully tagged sec-eng-special/tang-operator:v1.0.9
-docker push sec-eng-special/tang-operator:v1.0.9
+Successfully tagged sec-eng-special/tang-operator:v1.0.10
+docker push sec-eng-special/tang-operator:v1.0.10
 The push refers to repository [quay.io/sec-eng-special/tang-operator]
-7910991.0.9a: Pushed
+7910991.0.10a: Pushed
 417cb9b79ade: Layer already exists
-v1.0.9: digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
+v1.0.10: digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
 ```
 
 It is possible to use `podman` instead of `docker`:
 
 ```bash
-$ make podman-build podman-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.9"
+$ make podman-build podman-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.10"
 ...
 Successfully built 4a88ba8e6426
-Successfully tagged sec-eng-special/tang-operator:v1.0.9
-podman push sec-eng-special/tang-operator:v1.0.9
+Successfully tagged sec-eng-special/tang-operator:v1.0.10
+podman push sec-eng-special/tang-operator:v1.0.10
 The push refers to repository [quay.io/sec-eng-special/tang-operator]
-7910991.0.9a: Pushed
+7910991.0.10a: Pushed
 417cb9b79ade: Layer already exists
-v1.0.9: digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
+v1.0.10: digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
 ```
 
 In case a new release is planned to be done, the steps to follow will be:
@@ -254,23 +255,23 @@ index 9a41c6a..db12a82 100644
 @@ -3,7 +3,7 @@
 # To re-generate a bundle for another specific version without changing the
 # standard setup, you can:
-# - use the VERSION as arg of the bundle target (e.g. make bundle VERSION=1.0.9)
-# - use environment variables to overwrite this value (e.g. export VERSION=1.0.9)
+# - use the VERSION as arg of the bundle target (e.g. make bundle VERSION=1.0.10)
+# - use environment variables to overwrite this value (e.g. export VERSION=1.0.10)
 -VERSION ?= 1.0.8
-+VERSION ?= 1.0.9
++VERSION ?= 1.0.10
 ```
 
 Apart from previous changes, it is recommended to generate a "latest" tag for tang-operator bundle:
 
 ```bash
-$ docker tag quay.io/sec-eng-special/tang-operator-bundle:v1.0.9 quay.io/sec-eng-special/tang-operator-bundle:latest
+$ docker tag quay.io/sec-eng-special/tang-operator-bundle:v1.0.10 quay.io/sec-eng-special/tang-operator-bundle:latest
 $ docker push quay.io/sec-eng-special/tang-operator-bundle:latest
 ```
 
 In case `podman` is being used:
 
 ```bash
-$ podman tag quay.io/sec-eng-special/tang-operator-bundle:v1.0.9 quay.io/sec-eng-special/tang-operator-bundle:latest
+$ podman tag quay.io/sec-eng-special/tang-operator-bundle:v1.0.10 quay.io/sec-eng-special/tang-operator-bundle:latest
 $ podman push quay.io/sec-eng-special/tang-operator-bundle:latest
 ```
 
@@ -280,28 +281,28 @@ Compile Tang operator code, specifying new version,
 by using **make docker-build** command:
 
 ```bash
-$ make docker-build docker-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.9"
+$ make docker-build docker-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.10"
 ...
-Successfully tagged sec-eng-special/tang-operator:v1.0.9
-docker push sec-eng-special/tang-operator:v1.0.9
+Successfully tagged sec-eng-special/tang-operator:v1.0.10
+docker push sec-eng-special/tang-operator:v1.0.10
 The push refers to repository [quay.io/sec-eng-special/tang-operator]
 9ff8a4099c67: Pushed
 417cb9b79ade: Layer already exists
-v1.0.9: digest: sha256:01620ab19faae54fb382a2ff285f589cf0bde6e168f14f07 size: 739
+v1.0.10: digest: sha256:01620ab19faae54fb382a2ff285f589cf0bde6e168f14f07 size: 739
 ```
 
 And, in case `podman` is being used instead of `docker`:
 
 ```bash
-$ make podman-build podman-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.9"
+$ make podman-build podman-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.10"
 ...
 Successfully built 4a88ba8e6426
-Successfully tagged sec-eng-special/tang-operator:v1.0.9
-podman push sec-eng-special/tang-operator:v1.0.9
+Successfully tagged sec-eng-special/tang-operator:v1.0.10
+podman push sec-eng-special/tang-operator:v1.0.10
 The push refers to repository [quay.io/sec-eng-special/tang-operator]
-7910991.0.9a: Pushed
+7910991.0.10a: Pushed
 417cb9b79ade: Layer already exists
-v1.0.9: digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
+v1.0.10: digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
 ```
 
 - <ins>Bundle push</ins>:
@@ -311,15 +312,15 @@ the bundle with **make bundle**, specifying appropriate image,
 and push it with **make bundle-build bundle-push**:
 
 ```bash
-$ make bundle IMG="quay.io/sec-eng-special/tang-operator:v1.0.9"
-$ make bundle-build bundle-push BUNDLE_IMG="quay.io/sec-eng-special/tang-operator-bundle:v1.0.9"
+$ make bundle IMG="quay.io/sec-eng-special/tang-operator:v1.0.10"
+$ make bundle-build bundle-push BUNDLE_IMG="quay.io/sec-eng-special/tang-operator-bundle:v1.0.10"
 ...
-docker push sec-eng-special/tang-operator-bundle:v1.0.9
+docker push sec-eng-special/tang-operator-bundle:v1.0.10
 The push refers to repository [quay.io/sec-eng-special/tang-operator-bundle]
 02e3768cfc56: Pushed
 df0c8060d328: Pushed
 84774958bcf4: Pushed
-v1.0.9: digest: sha256:925c2f844f941db2b53ce45cba9db7ee0be613321da8f0f05d size: 939
+v1.0.10: digest: sha256:925c2f844f941db2b53ce45cba9db7ee0be613321da8f0f05d size: 939
 make[1]: Leaving directory '/home/user/RedHat/TASKS/TANG_OPERATOR/tang-operator'
 ```
 
@@ -328,15 +329,15 @@ In case the operator bundle is required to be pushed, generate the bundle with *
 specifying appropriate image, and push it with **make podman-bundle-build podman-bundle-push**:
 
 ```bash
-$ make bundle IMG="quay.io/sec-eng-special/tang-operator:v1.0.9"
-$ make podman-bundle-build podman-bundle-push BUNDLE_IMG="quay.io/sarroutb/tang-operator-bundle:v1.0.9"
+$ make bundle IMG="quay.io/sec-eng-special/tang-operator:v1.0.10"
+$ make podman-bundle-build podman-bundle-push BUNDLE_IMG="quay.io/sarroutb/tang-operator-bundle:v1.0.10"
 ...
-podman push sec-eng-special/tang-operator-bundle:v1.0.9
+podman push sec-eng-special/tang-operator-bundle:v1.0.10
 The push refers to repository [quay.io/sec-eng-special/tang-operator-bundle]
 02e3768cfc56: Pushed
 df0c8060d328: Pushed
 84774958bcf4: Pushed
-v1.0.9: digest: sha256:925c2f844f941db2b53ce45cba9db7ee0be613321da8f0f05d size: 939
+v1.0.10: digest: sha256:925c2f844f941db2b53ce45cba9db7ee0be613321da8f0f05d size: 939
 make[1]: Leaving directory '/home/user/RedHat/TASKS/TANG_OPERATOR/tang-operator'
 ```
 
@@ -376,15 +377,15 @@ In order to cross compile tang-operator, prepend **GOARCH** with required archit
 **make docker-build**:
 
 ```bash
-$ GOARCH=ppc64le make docker-build docker-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.9"
+$ GOARCH=ppc64le make docker-build docker-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.10"
 ...
 Successfully built 4a88ba8e6426
-Successfully tagged sec-eng-special/tang-operator:v1.0.9
-docker push sec-eng-special/tang-operator:v1.0.9
+Successfully tagged sec-eng-special/tang-operator:v1.0.10
+docker push sec-eng-special/tang-operator:v1.0.10
 The push refers to repository [quay.io/sec-eng-special/tang-operator]
-7910991.0.9a: Pushed
+7910991.0.10a: Pushed
 417cb9b79ade: Layer already exists
-v1.0.9: digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
+v1.0.10: digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739
 ```
 Examples of architectures to cross-compile are:
 * `ppc64le`
@@ -401,9 +402,9 @@ recommended way:
 
 ```bash
 $ operator-sdk cleanup tang-operator
-INFO[0001] subscription "tang-operator-v1.0.9-sub" deleted
+INFO[0001] subscription "tang-operator-v1.0.10-sub" deleted
 INFO[0001] customresourcedefinition "tangservers.daemons.redhat.com" deleted
-INFO[0002] clusterserviceversion "tang-operator.v1.0.9" deleted
+INFO[0002] clusterserviceversion "tang-operator.v1.0.10" deleted
 INFO[0002] catalogsource "tang-operator-catalog" deleted
 INFO[0002] operatorgroup "operator-sdk-og" deleted
 INFO[0002] Operator "tang-operator" uninstalled
@@ -493,7 +494,7 @@ However, scorecard tests can be executed manually. In order to execute these tes
 run next command:
 
 ```bash
-$ operator-sdk scorecard -w 60s quay.io/sec-eng-special/tang-operator-bundle:v1.0.9
+$ operator-sdk scorecard -w 60s quay.io/sec-eng-special/tang-operator-bundle:v1.0.10
 ...
 Results:
 Name: olm-status-descriptors
@@ -520,7 +521,7 @@ Name: olm-bundle-validation
 State: pass
 ```
 
-As it can be observed, execution of operator-sdk scorecard tests are passing successfully in latest released version (v1.0.9).
+As it can be observed, execution of operator-sdk scorecard tests are passing successfully in latest released version (v1.0.10).
 
 ## Links
 

bundle/manifests/tang-operator.clusterserviceversion.yaml

@@ -25,10 +25,10 @@ metadata:
         }
       ]
     capabilities: Basic Install
-    createdAt: "2024-05-07T08:38:26Z"
+    createdAt: "2024-07-22T14:20:44Z"
     operators.operatorframework.io/builder: operator-sdk-v1.33.0
     operators.operatorframework.io/project_layout: go.kubebuilder.io/v4
-  name: tang-operator.v1.0.9
+  name: tang-operator.v1.0.10
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -328,7 +328,7 @@ spec:
                 - --leader-elect
                 command:
                 - /manager
-                image: quay.io/sec-eng-special/tang-operator:v1.0.9
+                image: quay.io/sec-eng-special/tang-operator:v1.0.10
                 livenessProbe:
                   httpGet:
                     path: /healthz
@@ -411,4 +411,4 @@ spec:
   maturity: alpha
   provider:
     name: Red Hat
-  version: 1.0.9
+  version: 1.0.10

config/manager/kustomization.yaml

@@ -13,4 +13,4 @@ kind: Kustomization
 images:
 - name: controller
   newName: quay.io/sec-eng-special/tang-operator
-  newTag: v1.0.9
+  newTag: v1.0.10