Generate Konflux pipelines

[pierDipi]

Follow up to #161

• Generate pipeline and pipeline runs for push and PR referencing the Konflux Docker build pipeline (downloaded from https://github.com/konflux-ci/build-definitions/blob/main/pipelines/docker-build-oci-ta/README.md, see updated cmd/konflux-gen/README.md in the PR)

[pierDipi]

/cc @mgencur @creydr

[mgencur]

I haven't fully reviewed this but I can see there's just one type of Pipeline. I was working on openshift-knative/serverless-operator#2707 to build all images there and figured there are two Pipelines that are slightly different. I call them serverless-image and serverless-index (the Pipeline for the index image is slightly different). Maybe @creydr could shed some light on the difference as I just copied them from the original pipelines.
The index image is probably not considered in this PR. Just something to think about for the future.

[creydr]

I haven't fully reviewed this but I can see there's just one type of Pipeline. I was working on openshift-knative/serverless-operator#2707 to build all images there and figured there are two Pipelines that are slightly different. I call them serverless-image and serverless-index (the Pipeline for the index image is slightly different). Maybe @creydr could shed some light on the difference as I just copied them from the original pipelines. The index image is probably not considered in this PR. Just something to think about for the future.

The serverless-index pipeline is a bit different, because it has additional steps to verify the file based catalog of the index. This was mostly auto generated, as Konflux recognized it as an index build (therefor I needed to reference a devfile, which I reverted, after we had the pipeline generated (openshift-knative/serverless-operator@2a6573d), as this made things more complicated and was not needed anymore (as we had the FBC related tasks in the pipeline)).

[pierDipi]

That pipeline will need to be special cased, it's this one basically https://github.com/konflux-ci/build-definitions/tree/main/pipelines/fbc-builder

[creydr]

One other thing we should keep in mind is to only trigger a pipeline on relevant changes for the component. Otherwise this could trigger endless renovate PRs. See from openshift-knative/serverless-operator#2674

Prevent endless renovate PRs as serverless-operator and serverless-bundle are in the same repository (As both are in the same repository, an update on the bundle (e.g. via an automated renovate PR to update the image references) triggers a new build of the serverless-operator. As this results in a new image tag, a new renovate PR for the CSV is sent again (-> endless loop).): openshift-knative/serverless-operator@09a1470

[pierDipi]

But for now, I'm focusing on dependents component, SO will come next

[creydr]

But for now, I'm focusing on dependents component, SO will come next

ACK. Just wanted to mention it in this context, so we don't forget about it

[pierDipi]

Let me know if the PR looks ok and code is clean/readable enough as I'd like to try it out for eventing core

[creydr]

Only to make sure I understand this correctly: this is the "default-custom" pipeline from Konflux?

[pierDipi]

Yes, I think so

[pierDipi]

Actually, it's the new one that is not using PVC for storing artifacts and should solve our issue with PV/PVC Quota

[creydr]

LGTM from my side

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: creydr, pierDipi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [creydr,pierDipi]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment