[KOGITO-9103] [KSW-Operator] Create the cekit image descriptor for Op…

[davidesalerno]

…erator bundle image

Description of the change:

Motivation for the change:

Checklist

• Add or Modify a unit test for your change
• Have you verified that tall the tests are passing?

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

[kie-ci]

Openshift tests job #39 was: FAILURE
Possible explanation: Pipeline failure or project build failure

Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/39/display/redirect
See console log:

Console Logs

[2/2] STEP 4/10: LABEL description="Runtime Image for the Operator" io.cekit.version="4.7.0" summary="Runtime Image for the Operator"
[2/2] STEP 5/10: USER root
[2/2] STEP 6/10: RUN [ ! -d /tmp/scripts ] || rm -rf /tmp/scripts
[2/2] STEP 7/10: RUN [ ! -d /tmp/artifacts ] || rm -rf /tmp/artifacts
[2/2] STEP 8/10: USER 1001
[2/2] STEP 9/10: WORKDIR /usr/local/bin
[2/2] STEP 10/10: ENTRYPOINT ["manager"]
[2/2] COMMIT sonataflow-serverless-operator:2.0.0-snapshot
Getting image source signatures
Copying blob sha256:4deb43649c6646648232e22a083fede21435efe5a0bbef767edf7034715444d1
Copying blob sha256:aa23ff5cc4433df8af2867758040c4b3a9dd2e13b5f97aed8d9331bc78d0b387
Copying config sha256:33471612c4f316af63f5cc36e4e81b810126c80cb77e2a404008ed0bed93250c
Writing manifest to image destination
Storing signatures
--> 33471612c4f
Successfully tagged localhost/sonataflow-serverless-operator:2.0.0-snapshot
Successfully tagged localhost/sonataflow-serverless-operator:latest
33471612c4f316af63f5cc36e4e81b810126c80cb77e2a404008ed0bed93250c
�[32m2023-06-20 17:11:23,973 podman.py:62 INFO Image built and available under following tags: sonataflow-serverless-operator:2.0.0-snapshot, sonataflow-serverless-operator:latest�[0m
�[32m2023-06-20 17:11:23,974 cli.py:501 INFO Finished!�[0m
podman tag kogito-serverless-operator image-registry.openshift-image-registry.svc:5000/openshift/kogito-serverless-operator:pr-991fe9d
Error: kogito-serverless-operator: image not known
make: *** [Makefile:184: container-build] Error 125
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Push Operator Image(s) to Openshift Registry)
Stage "Push Operator Image(s) to Openshift Registry" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Run e2e tests)
Stage "Run e2e tests" skipped due to earlier failure(s)
[Pipeline] stage
[Pipeline] { (Running e2e tests)
Stage "Run e2e tests" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] script
[Pipeline] {
[Pipeline] sh
+ wget --no-check-certificate -qO - https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/39/api/json
[Pipeline] readJSON
[Pipeline] sh

[mareknovotny]

what is holding this PR from merging? Is there any remaining work here? Do you know @ricardozanini ?

[ricardozanini]

@mareknovotny there are a few questions unanswered by Davide. I'll take this work since it looks like we don't have anyone else to do this work. But on my timeframe.

[mareknovotny]

i guess @davidesalerno can answer them if they are needed ;)

[spolti]

@mareknovotny there are a few questions unanswered by Davide. I'll take this work since it looks like we don't have anyone else to do this work. But on my timeframe.

I think we can merge this one as address any minor issue later.
As it refers to prod builds only, it would not affect the current releases nor introduce bugs.

[davidesalerno]

@ricardozanini I reported here the answers we agreed on in our pasts weekly alignments.
I think that as soon as the CVP tests are fine we should merge this PR and eventually open some improvement tasks to tweak some points (like the Makefile, if it is possible) because doing everything in one shot it is blocking this change and it is taking a lot of efforts to regaling it to the latest main version every time.

[ricardozanini]

@davidesalerno sure thing, just let me know when it's ready.