Collaboration with OKD Working Group to Build SCOS Artifacts

[JaimeMagiera]

Greetings,

I'd like to start a discussion on the possibility of the OKD and FCOS Working Groups collaborating on the building of SCOS artifacts. The OKD Working Group is looking for a home for SCOS builds. We have the following goals in mind:

• Host SCOS builds on infrastructure that is visible to the public and that provides an opportunity for community members to contribute (after some learning)

• Provide SCOS artifacts for a variety of platforms, similar to FCOS

• Ultimately move OKD to be simply being a layer on top of SCOS

In exchange, we could provide FCOS with volunteers to help the overall CoreOS build initiative.

Along these lines, we have a couple questions for you:

• What barriers do you see to the FCOS infrastructure building SCOS, both technical and effort-wise?

• If we enlisted volunteers to contribute to the overall CoreOS build effort, where would you need them most?

• Is FCOS planning on moving builds to Konflux? If so, do you have a timeline?

These are just some initial thoughts to get a public conversation going.

Warm regards,

Jaime

[travier]

My first thought would be that it would be best hosted and built on CentOS infrastructure as this is CentOS Stream CoreOS after all (SCOS).

[dustymabe]

My first thought would be that it would be best hosted and built on CentOS infrastructure as this is CentOS Stream CoreOS after all (SCOS).

ehh. I think there was more value in that in the past when the CentOS infrastructure and responsible infra teams weren't combined with Fedora's. I think (if we do this) we suggest to locate the building infra where it's most convenient, collaborating with the community infra team along the way.

[jbtrystram]

This issue was discussed in 2024/09/18 community meeting.
Right now there are still a lot of unknowns variables, but we will help to setup an SCOS pipeline once details have been decided by the SCOS community.
Right now the main missing things are :
1 - where to run the pipeline (needs a openshift/okd/k8s cluster)
2 - where to publish the AMIs and other artifacts
3 - an S3 bucket to publish the builds

See the meeting notes for more detail : https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-09-18/fedora-coreos-meeting.2024-09-18-16.31.log.html

Feel free to update this issue so it gets bring up again in a next community meeting :)

[Conan-Kudo]

My first thought would be that it would be best hosted and built on CentOS infrastructure as this is CentOS Stream CoreOS after all (SCOS).

ehh. I think there was more value in that in the past when the CentOS infrastructure and responsible infra teams weren't combined with Fedora's. I think (if we do this) we suggest to locate the building infra where it's most convenient, collaborating with the community infra team along the way.

They aren't combined even now. CentOS infrastructure has a couple of folks, and Fedora infrastructure has a few other folks, but there's no overlap.

[JaimeMagiera]

@Conan-Kudo Is the an OpenShift cluster available in either build stack to run a pipeline on?

[Conan-Kudo]

The CentOS CI OpenShift is capable of running Tekton pipelines. Information about it is here: https://sigs.centos.org/guide/ci/#openshift

The CentOS Hyperscale SIG uses OpenShift for some things, and the CentOS Cloud SIG can request a namespace to run SCOS stuff there if it desires to do so.