Do not update this Epic/Tasks directly. The template should be cloned and applied to the onboarding of your operator

Cloning and Customizing the Template

⚠️ DO NOT update the original Epic/Tasks directly. The template must be cloned and applied to your specific operator's OLMv1 adoption.

1. Clone the Template: Go to the template issue, select 'More' from the top menu, and click 'Clone EPIC and Children' from the drop-down.
2. Locate and Customize: After cloning, find the new Epic (it will be linked under Issue Links - is cloned by on the original template page). Select the cloned Epic (e.g., "[\{*}Operator Name] Red Hat Operator Base Image Change to UBI Minimal (Template)"). Immediately update the Summary, Epic Name, and *Description with your operator's specific information.

Moving the Cloned Epic and Tasks to Your Project

To begin work, you should move the Cloned Epic and all its child tasks to your own Jira Project using the Bulk Edit feature.

• Search for Issues: Use the Jira search bar to find the cloned Epic and all its sub-tasks. Replace your cloned Epic ID with the actual ID ( Eg. id in (PLMPGM-3772) OR id in childIssuesOf(PLMPGM-3772) order by Rank ASC).
  • id in (your cloned Epic ID) OR id in childIssuesOf(your cloned Epic ID) order by Rank ASC

• Start Bulk Change: Once the search results populate, go to Tools (on the top right corner)
  • Bulk Change All Tasks.

• Move the Issues:
  • Select Move Tasks.
  • Select your JIRA Project as the new destination.
  • Crucially, during the move process, associate all the tasks to the Epic Link (the cloned Epic you created in Part 1) to maintain the hierarchy.
  • Once you have Epic moved to your Jira project, please link it to OCPSTRAT-2553 (Please use Is Triggered by)

***********************************************************

Description:

This task is to track the mandatory transition of our operator and operand images to the UBI Minimal base image, as part of the wider initiative to reduce CVE noise and improve security posture. This change must be completed for all images targeting the OpenShift 4.21 release or later.

Action Required:

1. Base Image Change: Update the base image specified in the Containerfile/Dockerfile from the current Red Hat operator image to UBI Minimal.
2. Package Manager Update: Replace the DNF package manager with micro DNF in all build instructions for installing packages.
   Note: UBI Minimal does not include the Python runtime required by DNF.
3. Verification: Test the resulting operator and operand images to ensure no regression in functionality and that all necessary dependencies are correctly installed using microdnf.

Scope of Change:

• In Scope: All operator and operand images maintained and built by the owning team.
• Out of Scope: Dependencies pulled from RHEL AppStreams (e.g., Postgres, Redis) which are maintained by the RHEL team.

Acceptance Criteria (Definition of Done):

• All in-scope images have successfully been rebuilt using the UBI Minimal base image.

• The use of microdnf has been verified in the image build process.

• New images have been tested and confirmed to be fully functional.

• The necessary PRs for the changes have been merged.