Prow This approach would continue to leverage Prow as the OKD build system. Images would be built pre-submit (as CI on PRs) and post-submit (on merge, promoted to OKD ImageStream) Pros Direct feedback to devs (on status) through GitHub UI Source of truth build metadata from Prow Prow has ability to replace FROM directives in Dockerfiles Continuous builds (ie. components are rebuilt immediately after they've been changed)

Notes on building and maintaining the Cloud SIG rpms for OKD. Build Targets: c9s-sig-cloud-okd-4.13 c9s-sig-cloud-okd-4.14 Requires: https://git.centos.org/centos-git-common checked out in $PATH

OS Image Builds tekton pipeline for sagano/bootc/rpm-ostree/layered builds, productization for RHCOS 10 MCO support for sagano RPM Builds Non-RHEL package builds and packit.dev automation in CentOS Streamconmon-rs cri-o cri-tools

Hello everyone! I'm pleased to (re-)introduce myself here, and announce the creation of the OKD Streams team. I've been working in OpenShift Engineering for around 4 years now, with various stops in the CoreOS, MCO, WMCO and SPLAT teams. As one of the long-time maintainers of OKD, OpenShift's Open Source community edition, I'm pleased to announce my new role as Team Lead of the OKD Streams Team. OKD Streams: The Mission At a high level, we want OKD Streams to be for OpenShift, what CentOS Stream is for RHEL: A place to collaborate and incubate upstream of the product. Specifically, we want to improve the readiness signal for RHEL CoreOS by running daily builds of CentOS Stream CoreOS (aka SCOS), which can be seen like a preview build of future RHCOS. Hey this is me the OKD Stream teammission

Validate Pick a nightly from https://origin-release.ci.openshift.org/#4.12.0-0.okd-scos (for 4.next, pick one from https://origin-release.ci.openshift.org/#4.13.0-0.okd-scos) Run the install with cluster-bot and ensure it's ready to be promoted; log in and check branding:launch registry.ci.openshift.org/origin/release-scos:<NIGHTLY> Export RELEASE env:export RELEASE="4.12.0-0.okd-scos-2022-10-22-232744" Check signatures:oc adm release info registry.ci.openshift.org/origin/release-scos:${RELEASE} Copy Digest from output (taking away the sha256: prefix)... Digest: sha256:0132da68b7bc49ae27202585392ad1f6ee4951e0255627c15017775c6c9e33a6 ...

CentOS Stream CoreOS (SCOS) is a Linux distribution built from CentOS Stream RPM packages, and focused on running container-based workloads with Kubernetes. It is part of the SCOS Stream of OKD, the Kubernetes community distribution of OpenShift, co-maintained by the CentOS Cloud SIG and the OKD Working Group. In this presentation, we'll present the technologies and methodologies driving the CentOS Stream CoreOS (SCOS) release engineering, and the Cloud-Native architecture we leverage to package the operating system that runs Kubernetes/OKD. We'll show how this framework, powered by Tekton pipelines and operated via GitOps, can enable, thanks to rpm-ostree, the CoreOS Assembler and the Layering model, delivery scenarios for different OSes beyond the Cloud-Native ones: IoT, multimedia, automotive, thin-client-based environments. Users can derive their own purpose-driven variants by maintaining a common multi-arch base OS, distributed as a bootable Open Container Image (OCI).

In order to reproduce this locally, I changed the {manifest,extensions}.yaml symlinks for point to -c9s.yaml like in the pipeline In the extensions/Dockerfile, I added a rpm -qa :RUN rpm -qa && rpm-ostree compose extensions --rootfs=/ --output-dir=/usr/share/rpm-ostree/extensions/ {manifest,extensions}.yaml also removed the ARG COSA stuff from extensions/Dockerfile Then, try build with a good baseos: [lorbus@t14s os]$ podman build --from quay.io/okd/centos-stream-coreos-9@sha256:38e4a95a7370c793e0a083c1ce432be09f2527a78f8a047c1a0e2154a46ae2ce -f extensions/Dockerfile . [1/3] STEP 1/5: FROM quay.io/okd/centos-stream-coreos-9@sha256:38e4a95a7370c793e0a083c1ce432be09f2527a78f8a047c1a0e2154a46ae2ce AS os [1/3] STEP 2/5: RUN mkdir /os

1 ... ** (gnome-network-displays:105984): DEBUG: 00:13:18.923: Got state change notification from streaming sink to state ND_SINK_STATE_STREAMING [New Thread 0x7fff99ffb640 (LWP 106169)] Thread 8 "pool-gnome-netw" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffdf7fe640 (LWP 105994)] 0x0000000000000000 in ?? () (gdb) bt #0 0x0000000000000000 in ()

[ 4.718008] rk808 0-001b: chip id: 0x0 [ 4.723160] rk808-regulator rk808-regulator: there is no dvs0 gpio [ 4.723747] rk808-regulator rk808-regulator: there is no dvs1 gpio [ 4.725335] vdd_center: supplied by vcc5v0_sys [ 4.726332] vdd_cpu_l: supplied by vcc5v0_sys [ 4.727034] vcc_ddr_s3: supplied by vcc5v0_sys [ 4.728062] vcc1v8_sys_s3: supplied by vcc5v0_sys [ 4.729056] LDO_REG1: supplied by vcc5v0_sys [ 4.729855] LDO_REG2: supplied by vcc5v0_sys [ 4.731529] vcc1v8_s3: supplied by vcc5v0_sys