Skip to content

refactor: cut os-stack.bst over to the Flatcar base and delete displaced FSDK elements #131

Closed

Description

@castrojo

Design: docs/superpowers/specs/2026-09-13-flatcar-base-migration-design.md (PR #123), phase 5. Blocked by the boot proof.

Clean cutover, no shims. os-stack.bst switches to flatcar/flatcar-usr.bst and these OS-payload dependencies are deleted:

public-stacks/runtime-minimal.bst, components/systemd.bst, dbus.bst, dbus-broker.bst, kmod.bst, shadow.bst, bootstrap/bash.bst, bluefin-server/uutils-coreutils.bst, components/openssh-systemd.bst, components/podman.bst, components/xfsprogs.bst, gnupg.bst, ca-certificates.bst, tzdata.bst, bluefin-server/linux-firmware-split.bst.

Kept unchanged - these are OS policy, not upstream software: os-release-flatcar.bst (now truthful rather than a compatibility fiction), os-sysupdate.bst, os-k0s-sysupdate.bst, os-sysupdate-keys.bst, os-networkd.bst, os-k0s-first-boot.bst, os-creds-prov.bst, os-kured-hook.bst, os-justfile.bst, os-issue.bst, os-image-info.bst, os-countme.bst, os-sshd-preset.bst, os-sshd-config.bst.

Also remove the os-base option once the Flatcar path is the only path.

Acceptance:

  • No FSDK userspace component remains in the OS payload graph; the installer keeps its FSDK stack.
  • just validate, pytest tests/unit, and the phase 4 boot gates all pass.
  • Affected skills updated; no orphaned references to the deleted elements.

Activity

  1. castrojo commented on Sep 13, 2026

    @castrojo
    ContributorAuthor

    Closing: superseded by the version-parity reframe in docs/superpowers/specs/2026-09-13-flatcar-base-migration-design.md (PR #123).

    There is no cutover to a Flatcar base, because the base stays FSDK 26.08. The displaced-elements table in this ticket assumed replacing FSDK userspace with Flatcar's tree; that is now an explicitly rejected alternative.

    The replacement work is phase 6, Substitution: working down the parity matrix, replace each imported reference binary with an FSDK-built component at Flatcar's version, re-running the boot proof after each swap. That needs the parity matrix first (#140), so it will be filed per-component rather than as one sweep.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions