Skip to content

Bake fips=1 into bootargs.cfg for FIPS provider images#627

Open
kirankn8 wants to merge 1 commit into
mainfrom
fips-provider
Open

Bake fips=1 into bootargs.cfg for FIPS provider images#627
kirankn8 wants to merge 1 commit into
mainfrom
fips-provider

Conversation

@kirankn8

Copy link
Copy Markdown
Contributor

Summary

  • When a non-FIPS slim ISO bootstraps a node and a FIPS provider image is flashed during cluster creation, there is no user-data cloud-config step to inject grub_options.extra_cmdline: "fips=1".
  • This adds fips=1 directly into /etc/cos/bootargs.cfg at build time when FIPS_ENABLED=true, ensuring the kernel boots in FIPS mode after the flash — no operator intervention needed.
  • Follows the exact same pattern already used for systemd.unified_cgroup_hierarchy=1 and selinux=0. Non-FIPS builds are unaffected.

Test plan

  • Build a FIPS provider image (FIPS_ENABLED=true) and verify /etc/cos/bootargs.cfg contains fips=1 in baseCmd
  • Build a non-FIPS provider image and verify fips=1 is NOT present in bootargs.cfg
  • Flash a FIPS provider image onto a node bootstrapped from a non-FIPS slim ISO, confirm /proc/sys/crypto/fips_enabled is 1 after reboot

🤖 Generated with Claude Code

When a non-FIPS slim ISO is used to bootstrap a node and a FIPS provider
image is flashed during cluster creation, there is no user-data/cloud-config
step to inject grub_options.extra_cmdline. This adds fips=1 directly into
/etc/cos/bootargs.cfg at build time when FIPS_ENABLED=true, following
the same pattern used for cgroup v2 and selinux=0.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant