As of this writing (2026-01-28), the bootc ConfigMap feature is still being litigated and implemented. The work contained within this epic cannot take place until this functionality has landed in bootc. See: https://github.com/bootc-dev/bootc/issues/22

Summary:  Bootc has opened a door for disk image customization via configmap. Switching from rpm-ostree to bootc, MCO should not only make sure all the functionality remains but also proactively extending its support to make sure all the customization power brought in by bootc are directed to the user, allowing them to fully maximize these advantages. This will involve creating a new user-side API for fetching admin-defined configuration and pairing MCO with a bootc day-2 configuration tool for applying the customizations. Interest and Proposals in which has been raised several times in previous discussions:

• Image-Based RHEL + OCP Journey
• Admin Defined Configuration with bootable containers
• OCP Day-2 Config Roadmap