# Introducing OKD Streams

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 team\
mission
what we're focusing on.
what you can do:

Ambassador
Playing
BYO Stream
Helping maintain build tooling

## What is OKD and OKD Streams?

At a high level, OKD is OpenShift's Open Source Community. OKD Streams are the build tooling and release streams for the different community builds. We refer to it as OKD Streams because OKD is not just one artifact or release stream. It also refers to the flexible Tekton tooling we use build and maintain them. We currently maintain three release streams:
* OKD on Fedora CoreOS Stable:
**OKD/FCOS**
* OKD on CentOS Stream CoreOS Stable:
**OKD/SCOS stable** (4.12)
* OKD on CentOS Stream CoreOS Next:
**OKD/SCOS .next** (4.13)

## Why OKD Streams

One stream of OKD that is critical to internal OpenShift engineering at this time is the stream based on the SCOS and the .next release branch (**OKD/SCOS .next** releases). We are using this OKD Stream to **improve our readiness signal** primarily for OCP, our partners, and our bare metal customers.

## How are OKD Streams built?

For the OKD/SCOS Streams, the [OKD CoreOS Tekton Pipeline](https://github.com/okd-project/okd-coreos-pipeline/) runs daily on a cluster hosted on [massopen.cloud](https://massopen.cloud/). The resulting bootimage artifacts are uploaded to an S3 bucket, and the OSTree-native container image is pushed to Quay.io. From there it is imported into OpenShift's Prow CI, where the release controller includes it in the next payload.

All the images that are components of the payload are still built in Prow.
There is however also a [Tekton Release Pipeline](https://github.com/okd-project/okd-release-pipeline/) that facilitates building any or all components of an OKD release payload.

OKD/SCOS releases (for both the stable and the next stream) are published sprintly in https://github.com/okd-project/okd-scos/releases

OKD/FCOS releases are published in https://github.com/okd-project/okd/releases/

Here’s a [short presentation](https://docs.google.com/presentation/d/1-sP8xQ60NPJoZffKkt4d8s5jgLgwxrkNyKakIR_CnlE).

Self-serve