Skip to content

OSDOCS-14733 Docs: Replace fcos references with scos #93587

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

OSDOCS-14733 Docs: Replace fcos references with scos #93587

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
50b524b
OSDOCS-14733 Docs: Replace fcos references with scos
May 20, 2025
71f44d0
edit per Prashanth684
May 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions _attributes/common-attributes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,12 +23,12 @@
:op-system-version-9: 9
:op-system-ai: Red{nbsp}Hat Enterprise Linux AI
ifdef::openshift-origin[]
:op-system-first: Fedora CoreOS (FCOS)
:op-system: FCOS
:op-system-lowercase: fcos
:op-system-base: Fedora
:op-system-base-full: Fedora
:op-system-version: 35
:op-system-first: CentOS Streams CoreOS (SCOS)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is "CentOS Stream" i believe, not "Streams". @ausil can correct me if i'm wrong.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It appears you are correct. Thanks!

:op-system: SCOS
:op-system-lowercase: scos
:op-system-base: SCOS
:op-system-base-full: CentOS Streams
:op-system-version: 9.x
endif::[]
:tsb-name: Template Service Broker
:kebab: image:kebab.png[title="Options menu"]
Expand Down
2 changes: 1 addition & 1 deletion modules/installation-gcp-user-infra-rhcos.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ The file name contains the {product-title} version number in the format
endif::openshift-origin[]
ifdef::openshift-origin[]
. Obtain the {op-system} image from the
link:https://getfedora.org/en/coreos/download?tab=cloud_operators&stream=stable[{op-system} Downloads] page
link:https://cloud.centos.org/centos/scos/9/prod/streams/[CentOS Cloud Images] page
endif::openshift-origin[]

. Create the Google storage bucket:
Expand Down
2 changes: 2 additions & 0 deletions modules/installation-minimum-resource-requirements.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -233,6 +233,7 @@ ifdef::vsphere[]
2. As with all user-provisioned installations, if you choose to use {op-system-base} compute machines in your cluster, you take responsibility for all operating system life cycle management and maintenance, including performing system updates, applying patches, and completing all other required tasks. Use of {op-system-base} 7 compute machines is deprecated and has been removed in {product-title} 4.10 and later.
endif::vsphere[]
--
ifndef::openshift-origin[]
[NOTE]
====
For {product-title} version 4.18, RHCOS is based on RHEL version 9.4, which updates the micro-architecture requirements. The following list contains the minimum instruction set architectures (ISA) that each architecture requires:
Expand All @@ -244,6 +245,7 @@ For {product-title} version 4.18, RHCOS is based on RHEL version 9.4, which upda

For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/9.2_release_notes/index#architectures[Architectures] ({op-system-base} documentation).
====
endif::openshift-origin[]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to add a section for OKD that from 4.20 SCOS is based on CentOS Stream 10, which bumps the micro-architecture version from previous versions

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Being that we're not referencing the older CS8 versions anymore, we can probably word this as from version 4.20 onward OKD will be on CS10.

Copy link
Contributor Author

@mburke5678 mburke5678 Oct 10, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ausil @spotzz
Do we need the full note in OKD, with the references to which updates the micro-architecture requirements and the list of the required minimum instruction set architectures (ISA)?
If so, do we have the information for CentOS 9.4 and 10?


ifdef::azure[]
[IMPORTANT]
Expand Down
2 changes: 1 addition & 1 deletion modules/installation-user-infra-machines-iso.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ link:https://mirror.openshift.com/pub/openshift-v4/x86_64/dependencies/rhcos/[{o
endif::ibm-power[]
endif::openshift-enterprise[]
ifdef::openshift-origin[]
link:https://getfedora.org/en/coreos/download?tab=metal_virtualized&stream=stable[{op-system}]
link:https://cloud.centos.org/centos/scos/9/prod/streams/[CentOS Cloud Images]
endif::openshift-origin[]
ifdef::ibm-power[]
link:https://mirror.openshift.com/pub/openshift-v4/ppc64le/dependencies/rhcos/[{op-system} image mirror]
Expand Down
2 changes: 1 addition & 1 deletion modules/installation-user-infra-machines-pxe.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ link:https://mirror.openshift.com/pub/openshift-v4/x86_64/dependencies/rhcos/[{o
endif::ibm-power[]
endif::openshift-enterprise[]
ifdef::openshift-origin[]
link:https://getfedora.org/en/coreos/download?tab=metal_virtualized&stream=stable[{op-system}]
link:https://cloud.centos.org/centos/scos/9/prod/streams/[CentOS Cloud Images]
endif::openshift-origin[]
ifdef::ibm-power[]
link:https://mirror.openshift.com/pub/openshift-v4/ppc64le/dependencies/rhcos/[{op-system} image mirror]
Expand Down
2 changes: 1 addition & 1 deletion modules/installation-vsphere-machines.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ The {op-system} images might not change with every release of {product-title}. Y
The filename contains the {product-title} version number in the format `rhcos-vmware.<architecture>.ova`.
endif::openshift-origin[]
ifdef::openshift-origin[]
. Obtain the {op-system} images from the link:https://getfedora.org/en/coreos/download?tab=metal_virtualized&stream=stable[{op-system} Downloads] page
. Obtain the {op-system} images from the link:https://cloud.centos.org/centos/scos/9/prod/streams/[CentOS Cloud Images] page
endif::openshift-origin[]

. In the vSphere Client, create a folder in your data center to store your VMs.
Expand Down
5 changes: 5 additions & 0 deletions modules/rhcos-about.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,12 @@
[id="rhcos-about_{context}"]
= About {op-system}

ifndef::openshift-origin[]
{op-system-first} represents the next generation of single-purpose container operating system technology by providing the quality standards of {op-system-base-full} with automated, remote upgrade features.
endif::openshift-origin[]
ifdef::openshift-origin[]
{op-system-first} represents the next generation of single-purpose container operating system technology by providing the quality standards of {op-system-base-full} with automated, remote upgrade features.
endif::openshift-origin[]

{op-system} is supported only as a component of {product-title} {product-version} for all {product-title} machines. {op-system} is the only supported operating system for all node types in {product-title}. {op-system} is deployed in {product-title} {product-version} in two general ways:

Expand Down