Initial Konflux setup

[creydr]

• Adding konflux manifests b050cbdb335cc16cdd5c4b7ea04fbd3c612b9021
  • eventing-controller
  • serverless-openshift-knative-operator
  • serverless-bundle
  • serverless-index
• Minor changes to work on Konflux:
  • Switch to public UBI image: ff5355ed32cb4bfe75a08ac118152f3f7bf73d72
  • Use registry.redhat.io/openshift4/ose-operator-registry as base image for catalog to fix FBC validate issues: 4052edb39f0bc57a8b37320632261d395065c878
  • Use non-scratch image as another parent image in bundle to address KFLUXBUGS-10: eba8c86ed1ccd2cdb4e3e2f81c7b3fd01eea506c
• Define component relationships for automatic image ref updates ("nudging"): 00da2f7fe800d31024450d965cdf3c57daf9632b
• initial image reference update in CSV: fae64fe3c9a8b2b2a59d5c686476903a090a11d8
• 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).): 09a1470710faf19d126a41abefe71bfd1e6cef36

https://github.com/openshift-knative/eventing/pull/616 for adding custom build pipelines for eventing-controller

[creydr]

/hold will do some tests to get around the infinite renovate PRs

[creydr]

/unhold as we have 09a1470710faf19d126a41abefe71bfd1e6cef36 to prevent infinite renovate PRs

[pierDipi]

Feel free to merge manually

/cc @ReToCode @mgencur

[pierDipi]

/cc @Kaustubh-pande @rudyredhat1

[openshift-ci[bot]]

@pierDipi: GitHub didn't allow me to request PR reviews from the following users: rudyredhat1.

Note that only openshift-knative members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to [this](https://github.com/openshift-knative/serverless-operator/pull/2674#issuecomment-2137097847): >/cc @Kaustubh-pande @rudyredhat1 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[Kaustubh-pande]

Hi, @creydr, this seems to me like everything is push to quay.io, for downstream/product-build if we want to use it, the builds are available at registry.redhat.io ? for this we need to do more configuration at konflux ? do you have any doc link for downstream/product-build of konflux ?

[creydr]

Hi, @creydr, this seems to me like everything is push to quay.io, for downstream/product-build if we want to use it, the builds are available at registry.redhat.io ? for this we need to do more configuration at konflux ? do you have any doc link for downstream/product-build of konflux ?

Hey @Kaustubh-pande, as clarified via Slack, for now the images are pushed to quay.io and at some point we aim to merge the downstream&midstream build pipelines into one Konflux build pipeline.

[pierDipi]

/lgtm

[openshift-ci[bot]]

[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](https://github.com/openshift-knative/serverless-operator/blob/konflux/OWNERS)~~ [pierDipi] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment