From b734b40e0a8413674fb229df766e7f711c5426b8 Mon Sep 17 00:00:00 2001 From: Sergio Arroutbi Date: Thu, 19 Sep 2024 10:53:40 +0200 Subject: [PATCH] Release version v1.0.11 (#344) Resolves: #343 Signed-off-by: Sergio Arroutbi --- Dockerfile | 2 +- Makefile | 2 +- README.md | 115 +++++++++--------- .../tang-operator.clusterserviceversion.yaml | 8 +- config/manager/kustomization.yaml | 2 +- 5 files changed, 65 insertions(+), 64 deletions(-) diff --git a/Dockerfile b/Dockerfile index 06adef3..b9e5384 100644 --- a/Dockerfile +++ b/Dockerfile @@ -1,5 +1,5 @@ # Build the manager binary -FROM golang:1.22 as builder +FROM golang:1.22.5 as builder WORKDIR /workspace # Copy the Go Modules manifests diff --git a/Makefile b/Makefile index ea0b9af..9feee0e 100644 --- a/Makefile +++ b/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.10 +VERSION ?= 1.0.11 # 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") diff --git a/README.md b/README.md index 9eb4bfa..a761f2d 100644 --- a/README.md +++ b/README.md @@ -96,6 +96,7 @@ Tang operator-bundle are: - v1.0.8: ServiceType / ClusterIP configuration through TangServer CR - v1.0.9: Golang dependencies update - v1.0.10: Libraries update +- v1.0.11: Libraries update, Update Go version (1.22 -> 1.22.5) ## Installation @@ -119,23 +120,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.10**, the command to execute +bundle. For example, in case latest version is **1.0.11**, the command to execute will be: ```bash -$ 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 +$ operator-sdk run bundle quay.io/sec-eng-special/tang-operator-bundle:v1.0.11 +INFO[0008] Successfully created registry pod: quay-io-sec-eng-special-tang-operator-bundle-v1.0.11 INFO[0009] Created CatalogSource: tang-operator-catalog INFO[0009] OperatorGroup "operator-sdk-og" created -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[0009] Created Subscription: tang-operator-v1.0.11-sub +INFO[0011] Approved InstallPlan install-lqf9f for the Subscription: tang-operator-v1.0.11-sub INFO[0011] Waiting for ClusterServiceVersion to reach 'Succeeded' phase -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" +INFO[0012] Waiting for ClusterServiceVersion "default/tang-operator.v1.0.11" +INFO[0018] Found ClusterServiceVersion "default/tang-operator.v1.0.11" phase: Pending +INFO[0020] Found ClusterServiceVersion "default/tang-operator.v1.0.11" phase: InstallReady +INFO[0021] Found ClusterServiceVersion "default/tang-operator.v1.0.11" phase: Installing +INFO[0031] Found ClusterServiceVersion "default/tang-operator.v1.0.11" phase: Succeeded +INFO[0031] OLM has successfully installed "tang-operator.v1.0.11" ``` To install latest multi-arch image, execute: ```bash @@ -151,10 +152,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.10 -INFO[0008] Successfully created registry pod: quay-io-sec-eng-special-tang-operator-bundle-v1.0.10 +$ operator-sdk run bundle --timeout 3m quay.io/sec-eng-special/tang-operator-bundle:v1.0.11 +INFO[0008] Successfully created registry pod: quay-io-sec-eng-special-tang-operator-bundle-v1.0.11 ... -INFO[0031] OLM has successfully installed "tang-operator.v1.0.10" +INFO[0031] OLM has successfully installed "tang-operator.v1.0.11" ``` Additionally, correct Tang operator installation can be observed if an output like @@ -164,7 +165,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.10 1/1 Running 0 90s +quay-io-tang-operator-bundle-v1.0.11 1/1 Running 0 90s tang-operator-controller-manager-5c9488d8dd-mgmsf 2/2 Running 0 52s ``` @@ -214,33 +215,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.10**, +To summarize, taking into account that the last released version is **v1.0.11**, compilation can be done with next command: ```bash -$ make docker-build docker-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.10" +$ make docker-build docker-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.11" ... Successfully built 4a88ba8e6426 -Successfully tagged sec-eng-special/tang-operator:v1.0.10 -docker push sec-eng-special/tang-operator:v1.0.10 +Successfully tagged sec-eng-special/tang-operator:v1.0.11 +docker push sec-eng-special/tang-operator:v1.0.11 The push refers to repository [quay.io/sec-eng-special/tang-operator] -7910991.0.10a: Pushed +7910991.0.11a: Pushed 417cb9b79ade: Layer already exists -v1.0.10: digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739 +v1.0.11: 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.10" +$ make podman-build podman-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.11" ... Successfully built 4a88ba8e6426 -Successfully tagged sec-eng-special/tang-operator:v1.0.10 -podman push sec-eng-special/tang-operator:v1.0.10 +Successfully tagged sec-eng-special/tang-operator:v1.0.11 +podman push sec-eng-special/tang-operator:v1.0.11 The push refers to repository [quay.io/sec-eng-special/tang-operator] -7910991.0.10a: Pushed +7910991.0.11a: Pushed 417cb9b79ade: Layer already exists -v1.0.10: digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739 +v1.0.11: digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739 ``` In case a new release is planned to be done, the steps to follow will be: @@ -256,23 +257,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.10) -# - use environment variables to overwrite this value (e.g. export VERSION=1.0.10) +# - use the VERSION as arg of the bundle target (e.g. make bundle VERSION=1.0.11) +# - use environment variables to overwrite this value (e.g. export VERSION=1.0.11) -VERSION ?= 1.0.9 -+VERSION ?= 1.0.10 ++VERSION ?= 1.0.11 ``` 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.10 quay.io/sec-eng-special/tang-operator-bundle:latest +$ docker tag quay.io/sec-eng-special/tang-operator-bundle:v1.0.11 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.10 quay.io/sec-eng-special/tang-operator-bundle:latest +$ podman tag quay.io/sec-eng-special/tang-operator-bundle:v1.0.11 quay.io/sec-eng-special/tang-operator-bundle:latest $ podman push quay.io/sec-eng-special/tang-operator-bundle:latest ``` @@ -282,28 +283,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.10" +$ make docker-build docker-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.11" ... -Successfully tagged sec-eng-special/tang-operator:v1.0.10 -docker push sec-eng-special/tang-operator:v1.0.10 +Successfully tagged sec-eng-special/tang-operator:v1.0.11 +docker push sec-eng-special/tang-operator:v1.0.11 The push refers to repository [quay.io/sec-eng-special/tang-operator] 9ff8a4099c67: Pushed 417cb9b79ade: Layer already exists -v1.0.10: digest: sha256:01620ab19faae54fb382a2ff285f589cf0bde6e168f14f07 size: 739 +v1.0.11: 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.10" +$ make podman-build podman-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.11" ... Successfully built 4a88ba8e6426 -Successfully tagged sec-eng-special/tang-operator:v1.0.10 -podman push sec-eng-special/tang-operator:v1.0.10 +Successfully tagged sec-eng-special/tang-operator:v1.0.11 +podman push sec-eng-special/tang-operator:v1.0.11 The push refers to repository [quay.io/sec-eng-special/tang-operator] -7910991.0.10a: Pushed +7910991.0.11a: Pushed 417cb9b79ade: Layer already exists -v1.0.10: digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739 +v1.0.11: digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739 ``` - Bundle push: @@ -313,15 +314,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.10" -$ make bundle-build bundle-push BUNDLE_IMG="quay.io/sec-eng-special/tang-operator-bundle:v1.0.10" +$ make bundle IMG="quay.io/sec-eng-special/tang-operator:v1.0.11" +$ make bundle-build bundle-push BUNDLE_IMG="quay.io/sec-eng-special/tang-operator-bundle:v1.0.11" ... -docker push sec-eng-special/tang-operator-bundle:v1.0.10 +docker push sec-eng-special/tang-operator-bundle:v1.0.11 The push refers to repository [quay.io/sec-eng-special/tang-operator-bundle] 02e3768cfc56: Pushed df0c8060d328: Pushed 84774958bcf4: Pushed -v1.0.10: digest: sha256:925c2f844f941db2b53ce45cba9db7ee0be613321da8f0f05d size: 939 +v1.0.11: digest: sha256:925c2f844f941db2b53ce45cba9db7ee0be613321da8f0f05d size: 939 make[1]: Leaving directory '/home/user/RedHat/TASKS/TANG_OPERATOR/tang-operator' ``` @@ -330,15 +331,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.10" -$ make podman-bundle-build podman-bundle-push BUNDLE_IMG="quay.io/sarroutb/tang-operator-bundle:v1.0.10" +$ make bundle IMG="quay.io/sec-eng-special/tang-operator:v1.0.11" +$ make podman-bundle-build podman-bundle-push BUNDLE_IMG="quay.io/sarroutb/tang-operator-bundle:v1.0.11" ... -podman push sec-eng-special/tang-operator-bundle:v1.0.10 +podman push sec-eng-special/tang-operator-bundle:v1.0.11 The push refers to repository [quay.io/sec-eng-special/tang-operator-bundle] 02e3768cfc56: Pushed df0c8060d328: Pushed 84774958bcf4: Pushed -v1.0.10: digest: sha256:925c2f844f941db2b53ce45cba9db7ee0be613321da8f0f05d size: 939 +v1.0.11: digest: sha256:925c2f844f941db2b53ce45cba9db7ee0be613321da8f0f05d size: 939 make[1]: Leaving directory '/home/user/RedHat/TASKS/TANG_OPERATOR/tang-operator' ``` @@ -378,15 +379,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.10" +$ GOARCH=ppc64le make docker-build docker-push IMG="quay.io/sec-eng-special/tang-operator:v1.0.11" ... Successfully built 4a88ba8e6426 -Successfully tagged sec-eng-special/tang-operator:v1.0.10 -docker push sec-eng-special/tang-operator:v1.0.10 +Successfully tagged sec-eng-special/tang-operator:v1.0.11 +docker push sec-eng-special/tang-operator:v1.0.11 The push refers to repository [quay.io/sec-eng-special/tang-operator] -7910991.0.10a: Pushed +7910991.0.11a: Pushed 417cb9b79ade: Layer already exists -v1.0.10: digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739 +v1.0.11: digest: sha256:c97bed08ab71556542602b008888bdf23ce4afd86228a07 size: 739 ``` Examples of architectures to cross-compile are: * `ppc64le` @@ -403,9 +404,9 @@ recommended way: ```bash $ operator-sdk cleanup tang-operator -INFO[0001] subscription "tang-operator-v1.0.10-sub" deleted +INFO[0001] subscription "tang-operator-v1.0.11-sub" deleted INFO[0001] customresourcedefinition "tangservers.daemons.redhat.com" deleted -INFO[0002] clusterserviceversion "tang-operator.v1.0.10" deleted +INFO[0002] clusterserviceversion "tang-operator.v1.0.11" deleted INFO[0002] catalogsource "tang-operator-catalog" deleted INFO[0002] operatorgroup "operator-sdk-og" deleted INFO[0002] Operator "tang-operator" uninstalled @@ -495,7 +496,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.10 +$ operator-sdk scorecard -w 60s quay.io/sec-eng-special/tang-operator-bundle:v1.0.11 ... Results: Name: olm-status-descriptors @@ -522,7 +523,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.10). +As it can be observed, execution of operator-sdk scorecard tests are passing successfully in latest released version (v1.0.11). ## Links diff --git a/bundle/manifests/tang-operator.clusterserviceversion.yaml b/bundle/manifests/tang-operator.clusterserviceversion.yaml index feac829..8112d2e 100644 --- a/bundle/manifests/tang-operator.clusterserviceversion.yaml +++ b/bundle/manifests/tang-operator.clusterserviceversion.yaml @@ -25,10 +25,10 @@ metadata: } ] capabilities: Basic Install - createdAt: "2024-07-22T14:20:44Z" + createdAt: "2024-09-18T14:19:06Z" operators.operatorframework.io/builder: operator-sdk-v1.33.0 operators.operatorframework.io/project_layout: go.kubebuilder.io/v4 - name: tang-operator.v1.0.10 + name: tang-operator.v1.0.11 namespace: placeholder spec: apiservicedefinitions: {} @@ -328,7 +328,7 @@ spec: - --leader-elect command: - /manager - image: quay.io/sec-eng-special/tang-operator:v1.0.10 + image: quay.io/sec-eng-special/tang-operator:v1.0.11 livenessProbe: httpGet: path: /healthz @@ -411,4 +411,4 @@ spec: maturity: alpha provider: name: Red Hat - version: 1.0.10 + version: 1.0.11 diff --git a/config/manager/kustomization.yaml b/config/manager/kustomization.yaml index a003218..a2cba6c 100644 --- a/config/manager/kustomization.yaml +++ b/config/manager/kustomization.yaml @@ -13,4 +13,4 @@ kind: Kustomization images: - name: controller newName: quay.io/sec-eng-special/tang-operator - newTag: v1.0.10 + newTag: v1.0.11