Changes/KonfluxFedoraBootc

Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.

Guidance
For details on how to fill out this form, see the documentation.

Report issues
To report an issue with this template, file an issue in the pgm_docs repo.

Using Konflux to build Fedora Bootc images

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

The Fedora Bootc initiative would like to start using the Konflux platform to build to the Fedora Bootc images. The goal of this change is to deploy a instance of Konflux https://konflux-ci.dev/ in Fedora's infrastructure and start using it to build Fedora Bootc images.

Owner

• Name: Clément Verna
• Email: <cverna@fedoraproject.org>

Current status

• Targeted release: Fedora Linux 42
• Last updated: 2024-06-25
• [Announced]
• [<will be assigned by the Wrangler> Discussion thread]
• FESCo issue: <will be assigned by the Wrangler>
• Tracker bug: <will be assigned by the Wrangler>
• Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

With the release of bootable containers, it is now possible to use the container build and release infrastructure for ostree editions. Fedora Bootc would like to make use of these capabilities and start to migrate to Konflux. The scope of this change for the Fedora 42 timeline is:

1. Get Konflux deployed in Fedora Infrastructure (we need help from Fedora Infra as well as the Konflux team). We need support for x86, aarch64, ppc64le and s390x architectures.
2. Integrate Konflux with Fedora Account System and create a namespace for Fedora Bootc.

Benefit to Fedora

1. This will introduce Konflux in Fedora's infrastructure and allow contributors to become more familiar with the platform.
2. This will allow for Fedora Bootc to be easier to customize, the build becomes a simple container build and contributors can easily duplicate the pipeline in Konflux.

Scope

• Proposal owners:

• Other developers:

• Release engineering: #Releng issue number

• Policies and guidelines: N/A (not needed for this Change)

• Trademark approval: N/A (not needed for this Change)

• Alignment with the Fedora Strategy:

Early Testing (Optional)

Do you require 'QA Blueprint' support? Y/N

Contingency Plan

• Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
• Contingency deadline: N/A (not a System Wide Change)
• Blocks release? N/A (not a System Wide Change), Yes/No

Documentation

N/A (not a System Wide Change)