KojiServiceImageBuilderRemoval
Announced
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
Summary
Since Fedora 43 there are two ways to interact with Red Hat Image Builder to build images. Local (on the Koji workers) or through an external service (through the service’s infrastructure). This proposal drops the service parts while keeping the Koji-local builds.
Owner
- Name: [[User:supakeen| Simon de vlieger]]
- Email: cmdr@supakeen.com
Detailed Description
Currently two plugins are deployed on Fedora Koji’s infrastructure to interact with Red Hat Image Builder. There’s koji-osbuild and koji-image-builder.
koji-osbuild tasks create API requests to Red Hat Image Builder’s API and the results of these tasks are attached to builds. koji-image-builder performs builds directly on Koji workers in the same way as Lorax, or Kiwi do.
In Fedora 43 we transitioned Editions and Spins using koji-osbuild to koji-image-builder. See [[Changes/KojiLocalImageBuilder]].
With that change proposal implemented no deliverables are produced with the Red Hat Image Builder service, however the team is still maintaining its infrastructure for it (builders that are used to build Fedora artifacts). Since this plugin is no longer in use we’d like to drop it from Fedora’s Koji configuration and afterwards to decommission the infrastructure maintained for it.
This means that users no longer have access to the osbuildImage task type in Koji; but can migrate to the imageBuilderBuild task type.
Current users of koji-osbuild have already been migrated to koji-image-builder but for completeness the following artifacts are produced by it since Fedora 43:
- ARM SIG’s Minimal disk images.
- Fedora IoT disk images.
- Fedora IoT Anaconda ISOs.
- Fedora IoT CoreOS installer ISOs.
Fedora IoT is the last to be building images with osbuildImage (for Fedora 42). We’ll coordinate with them that these are turned off after Fedora 43 final.
Feedback
None yet.
Benefit to Fedora
The benefit is mostly to the Image Builder team as we can decommission a chunk of our hardware. For Fedora the benefits are: fewer packages and simplified configuration on for Koji and Pungi and less confusion for those maintaining these systems.
Real benefits were mostly part of the previous change where we migrated Fedora off of the service and made the service obsolete. See [[Changes/KojiLocalImageBuilder]].
Scope
- Proposal owners:
** Create PR to remove Fedora 42 builds withosbuildImagefor Fedora IoT.
** Create PR to removeosbuildImageconfiguration and packages from Koji staging.
** Create PR to removeosbuildImageconfiguration and packages from Koji production. - Other developers: None.
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A
- Alignment with the Fedora Strategy: I don’t know.
Upgrade/compatibility impact
Not applicable for this change.
Early Testing (Optional)
Not applicable for this change.
How To Test
Not applicable for this change.
##User Experience
Not applicable for this change.
Dependencies
N/A
Contingency Plan
There is no contingency plan. Generally we don’t build the other releases for which this Koji plugin was used. If we do want to build them they can be built with the Koji local version instead.
Documentation
None.
Release Notes
Nothing will change in the distro itself.
Last edited by @amoloney 2025-09-25T17:05:56Z
Last edited by @amoloney 2025-09-25T17:05:56Z