Skip to content

blueprint: installer kernel args (RHEL-107495)#25

Closed
supakeen wants to merge 1 commit into
mainfrom
installer-kernel
Closed

blueprint: installer kernel args (RHEL-107495)#25
supakeen wants to merge 1 commit into
mainfrom
installer-kernel

Conversation

@supakeen

@supakeen supakeen commented Aug 5, 2025

Copy link
Copy Markdown
Member

Allows for the customization of kernel arguments as used by installer environments. Anaconda takes certain actions based on the kernel arguments supplied such as configuring the installed system with them.

We've had the ability to customize these for disk images for a while now. We also need them for installers.

@supakeen supakeen requested a review from a team as a code owner August 5, 2025 11:20
@supakeen supakeen marked this pull request as draft August 5, 2025 11:22
@supakeen

supakeen commented Aug 5, 2025

Copy link
Copy Markdown
Member Author

Draft since it wants: osbuild/image-builder#1727 first.


No longer necessary with the removal of the internal blueprint versions in images.

Allows for the customization of kernel arguments as used by installer
environments. Anaconda takes certain actions based on the kernel
arguments supplied such as configuring the installed system with
them.

We've had the ability to customize these for disk images for a while
now. We also need them for installers.

Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
@supakeen supakeen marked this pull request as ready for review August 8, 2025 05:42
SudoNopasswd []string `json:"sudo-nopasswd,omitempty" toml:"sudo-nopasswd,omitempty"`
Kickstart *Kickstart `json:"kickstart,omitempty" toml:"kickstart,omitempty"`
Modules *AnacondaModules `json:"modules,omitempty" toml:"modules,omitempty"`
Kernel *InstallerKernelCustomization `json:"kernel,omitempty" toml:"kernel,omitempty"`

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Maybe a short comment here (or in the commit message) why we need a new customization and we can't just use the existing "KernelCustomization" that are used for disk images. I don't know the details but maybe: // installer needs their own customizations so that we can tweak the installed system via the existing KernelCustomizations or something (assuming that is true and the reason of course :)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This is something we (@achilleas-k and me) wanted to discuss in this PR. We can do either approach.

In general for installers Anaconda will handle setting up the kernel arguments and bootloader for the system being installed, thus there's no need to separate them.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I see now that I only referred to this in the images counterpart of this PR: osbuild/image-builder#1727 (comment)

@achilleas-k

Copy link
Copy Markdown
Member

We decided we're dropping this, right? We'll instead apply the regular customizations.kernel.append to ISOs directly. Should we close this PR?

@supakeen

supakeen commented Aug 12, 2025

Copy link
Copy Markdown
Member Author

We decided we're dropping this, right? We'll instead apply the regular customizations.kernel.append to ISOs directly. Should we close this PR?

Yes, and rewrite the one in images to use those.

@supakeen supakeen closed this Aug 12, 2025
@achilleas-k achilleas-k deleted the installer-kernel branch August 12, 2025 12:38
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.

3 participants