feat(profiles): scaffold Fedora CoreOS + RHCOS catalog profiles#48
Merged
Conversation
Adds cataloged (not-yet-runnable) profiles for the CoreOS family, requested
by Angelo Puglisi ("RHCOS, those are the tricky ones"):
- vm/profiles/fedora-coreos-stable-6.14.yaml — the freely-available CoreOS
stand-in (no Red Hat pull secret).
- vm/profiles/rhcos-4.16-5.14.yaml — RHEL CoreOS / OpenShift 4.16 (RHEL 9.4
kernel, 5.14).
Both are marked non-runnable in ExecutionTransport(): CoreOS boots via
Ignition, not cloud-init, so the SSH executor cannot provision the validator
(same gap as flatcar). RHCOS additionally ships via the pull-secret-gated
OpenShift release payload. The matching RHEL/AlmaLinux 9 (5.14) profile
approximates the RHCOS kernel in the meantime; Fedora CoreOS is the runnable
stand-in to prove the CoreOS boot path once an Ignition bootstrap lands.
Profile-catalog docs and the ExecutionTransport test cover the new entries.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Scaffolds CoreOS-family kernel targets in the profile catalog, prompted by a maintainer request (Angelo Puglisi: "I'd love if it could check like RHCOS, those are the tricky ones").
vm/profiles/fedora-coreos-stable-6.14.yaml— Fedora CoreOS, the freely-available CoreOS stand-in (no Red Hat pull secret).vm/profiles/rhcos-4.16-5.14.yaml— RHEL CoreOS / OpenShift 4.16 (RHEL 9.4 kernel, 5.14).Honest status: cataloged, not runnable yet
These are roadmap entries, not a "supported" claim — same posture as the existing
talos/bottlerocket/flatcarprofiles.ExecutionTransport()marks both unsupported because:flatcar). Enabling them needs an Ignition-config bootstrap path in the QEMU executor.Why it's still useful now
The RHCOS kernel is the RHEL 9.4 kernel (5.14, heavily backported), so the matching RHEL / AlmaLinux 9 (5.14) profile already approximates it for BPF-load questions. Fedora CoreOS is the freely-available cousin and the natural runnable stand-in to prove the CoreOS/Ignition boot path before tackling the gated RHCOS image.
Changes
internal/vm/transport.go:fedora-coreos/fcosandrhcos/rhel-coreos→ unsupported with Ignition reasons.internal/vm/qemu_test.go: extended theExecutionTransporttable (adds flatcar + the four CoreOS cases).docs/profile-catalog.md: tier-3 entries + a Transport Notes paragraph.go test ./internal/vm/...green (profile catalog load/validate + transport).🤖 Generated with Claude Code