Red Hat Konflux kflux-prd-rh03 update coreos-assembler

[red-hat-konflux-kflux-prd-rh03]

Pipelines as Code configuration proposal

To start the PipelineRun, add a new comment with content /ok-to-test

For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun

To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Please follow the block sequence indentation style introduced by the proprosed PipelineRuns YAMLs, or keep using consistent indentation level through your customized PipelineRuns. When different levels are mixed, it will be changed to the proposed style.

[openshift-ci]

Hi @red-hat-konflux-kflux-prd-rh03[bot]. Thanks for your PR.

I'm waiting for a coreos member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[joelcapitao]

/retest

[joelcapitao]

/ok-to-test

[joelcapitao]

/retest

[jlebon]

Is that pipeline definition synced from anywhere/derived from any higher-level configuration? If so, where does that live?

[joelcapitao]

Is that pipeline definition synced from anywhere/derived from any higher-level configuration? If so, where does that live?

This PR is a consequence of applying the YAML files of [1] with oc/kubectl.
I basically ran oc apply -k coreos-assembler locally before submitting the MR.
Now that's it's merged, ArgoCD takes care of the synchronization automatically.

As you can see in [2], we requested Konflux to send the PR with this annotation (i.e more information in [3], in another context but you get the idea).
We could remove this annotation and submit the tekton files manually.

When done automatically, Pipeline-as-Code (one of the Konflux component) pulls the pipeline definition set in [4] from [5].
In this case, it's [6].
Also, all the tasks defined in those pipelines live in the same repo at [7].
So you can see this repo as the source of truth of Konflux for the default Tekton pipelines and tasks.

As you can see, the *-pull-request.yaml and *-push.yaml files are quite the same except the trigger definition. We could simplify this later by defining the whole pipeline in a single file, and calling it as ref in the two files e.g [8]

[1] https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/6797
[2] https://gitlab.cee.redhat.com/releng/konflux-release-data/-/blob/a8c8e079bd6127de01a1a599f5fa6b9415be0018/tenants-config/cluster/kflux-prd-rh03/tenants/coreos-tenant/coreos-assembler/components.yaml#L8
[3] https://konflux-ci.dev/docs/building/reconfiguring-build-pipeline/#reset-the-build-pipeline
[4] https://gitlab.cee.redhat.com/releng/konflux-release-data/-/blob/a8c8e079bd6127de01a1a599f5fa6b9415be0018/tenants-config/cluster/kflux-prd-rh03/tenants/coreos-tenant/coreos-assembler/components.yaml#L9
[5] https://github.com/konflux-ci/build-definitions/tree/main/pipelines
[6] https://github.com/konflux-ci/build-definitions/tree/main/pipelines/docker-build-multi-platform-oci-ta
[7] https://github.com/konflux-ci/build-definitions/tree/main/task
[8] https://github.com/jcapiitao/fcc/tree/main/.tekton

[joelcapitao]

/retest

[joelcapitao]

/override ci/prow/rhcos
as it's failing on coreos/rhel-coreos-config#20.

[openshift-ci]

@jcapiitao: Overrode contexts on behalf of jcapiitao: ci/prow/rhcos

Details

In response to this:

/override ci/prow/rhcos
as it's failing on coreos/rhel-coreos-config#20.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.