Skip to content

[release-4.20] OCPBUGS-77064: reduce MCO image size#5673

Open
openshift-cherrypick-robot wants to merge 2 commits intoopenshift:release-4.20from
openshift-cherrypick-robot:cherry-pick-5657-to-release-4.20
Open

[release-4.20] OCPBUGS-77064: reduce MCO image size#5673
openshift-cherrypick-robot wants to merge 2 commits intoopenshift:release-4.20from
openshift-cherrypick-robot:cherry-pick-5657-to-release-4.20

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #5657

/assign isabella-janssen

/cherrypick release-4.19 release-4.18 release-4.17

In lieu of mounting package caches at build-time, we should clear them
after package installation.

Because the DNF wrapper sets the repo configuration differently in local
vs. CI builds, this will only yield a ~44 MB reduction for local builds.
However, it will yield a ~1.2 GB reduction for images built by CI.
Early versions of Buildah and/or OpenShift Image Builder presumably did
not support path globbing for COPY directives, which required us to
create a tarball and copy it into the final image.

Although the tarball is deleted immediately after extraction, it still
persists as an image layer when building an image locally due to the
COPY directive. This unnecessary layer increases overall image size by
~480 MB. This is only the case for local image builds since
OpenShift CI is configured to squash the final image layers, which
makes this a non-issue for release images.
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-76823 has been cloned as Jira Issue OCPBUGS-77064. Will retitle bug to link to clone.
/retitle [release-4.20] OCPBUGS-77064: reduce MCO image size

Details

In response to this:

This is an automated cherry-pick of #5657

/assign isabella-janssen

/cherrypick release-4.19 release-4.18 release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot changed the title [release-4.20] OCPBUGS-76823: reduce MCO image size [release-4.20] OCPBUGS-77064: reduce MCO image size Feb 19, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 19, 2026
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-77064, which is invalid:

  • expected dependent Jira Issue OCPBUGS-76823 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #5657

/assign isabella-janssen

/cherrypick release-4.19 release-4.18 release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from djoshy and pablintino February 19, 2026 14:01
@isabella-janssen
Copy link
Member

/assign @cheesesashimi

Copy link
Member

@isabella-janssen isabella-janssen left a comment

Choose a reason for hiding this comment

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

/label backport-risk-assessed
/lgtm

Clean backport

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 19, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 19, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 19, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: isabella-janssen, openshift-cherrypick-robot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 19, 2026
@isabella-janssen
Copy link
Member

/verified later @sergiordlr,@ptalgulk01

This bug fix will be verified post-merge.

@isabella-janssen
Copy link
Member

/retest-required

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Feb 19, 2026
@openshift-ci-robot
Copy link
Contributor

@isabella-janssen: This PR has been marked to be verified later by @sergiordlr,@ptalgulk01.

Details

In response to this:

/verified later @sergiordlr,@ptalgulk01

This bug fix will be verified post-merge.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 25, 2026

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-op-ocl 2344eb1 link false /test e2e-gcp-op-ocl
ci/prow/bootstrap-unit 2344eb1 link false /test bootstrap-unit
ci/prow/e2e-gcp-op-part1 2344eb1 link true /test e2e-gcp-op-part1
ci/prow/e2e-gcp-op-part2 2344eb1 link true /test e2e-gcp-op-part2

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria verified-later

Projects

None yet

Development

Successfully merging this pull request may close these issues.