Skip to content
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

split-rhcos-into-layers: document /etc/os-release changes #1755

Merged
merged 1 commit into from
Feb 20, 2025
Merged

split-rhcos-into-layers: document /etc/os-release changes #1755

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
27 changes: 27 additions & 0 deletions enhancements/rhcos/split-rhcos-into-layers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -398,6 +398,33 @@ As such, the versioning change should be transparent to end-users, but on the
off chance that a customer is relying on the current semantics, we should still
announce it in the GA release notes.

### /etc/os-release

Previously, the node image used a heavily customized `/etc/os-release`, mutating
some key fields inherited from RHEL. A major theme of this enhancement and more
largely of the Image Mode effort is re-emphasizing the fact that RHCOS simply
builds on top of RHEL Image Mode. As such, many fields in `/etc/os-release` are
now left untouched.

Important fields that **will be different**:

Key|Old Value|New Value
---|---|---
VERSION|419.94.202412101440-0|9.6.20250203-0 (Plow)
Copy link
Member

Choose a reason for hiding this comment

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

Only thing I'm a little wary of is the text string here (Plow). I know that matches what RHEL does but could cause some issues for anyone relying on it only having the version itself in there.

That being said, if we think this is the right thing to do then now is the time to make that change.

Copy link
Member Author

Choose a reason for hiding this comment

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

I hope that nothing is parsing this today. They should instead be parsing VERSION_ID and/or OSTREE_VERSION which are meant to be machine-parsable.

VERSION_ID|4.19|9.6
OSTREE_VERSION|419.94.202412101440-0|9.6.20250203-0
ID|rhcos|rhel

Important fields that **remain the same**:

Key|Value
---|---
NAME|Red Hat Enterprise Linux CoreOS
PRETTY_NAME|Red Hat Enterprise Linux CoreOS $VERSION
VARIANT|CoreOS
VARIANT_ID|coreos
OPENSHIFT_VERSION|4.19

#### Hidden dependencies

Given that we're effectively removing packages from the bootimages, we may
Expand Down