OCPBUGS-66414: Fix cert-manager rebase to use per-platform images instead of multi-platform manifest lists

[ggiguash]

No description provided.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci-robot]

@ggiguash: This pull request references Jira Issue OCPBUGS-66414, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jogeo

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

Details

In response to this:

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.

[ggiguash]

/test ?

[openshift-ci]

@ggiguash: The following commands are available to trigger required jobs:

/test e2e-aws-ai-model-serving

/test e2e-aws-footprint-and-performance

/test e2e-aws-tests

/test e2e-aws-tests-arm

/test e2e-aws-tests-bootc

/test e2e-aws-tests-bootc-arm

/test e2e-aws-tests-bootc-periodic

/test e2e-aws-tests-bootc-periodic-arm

/test e2e-aws-tests-bootc-release

/test e2e-aws-tests-bootc-release-arm

/test e2e-aws-tests-bootc-upstream

/test e2e-aws-tests-bootc-upstream-arm

/test e2e-aws-tests-cache

/test e2e-aws-tests-cache-arm

/test e2e-aws-tests-periodic

/test e2e-aws-tests-periodic-arm

/test e2e-aws-tests-release

/test e2e-aws-tests-release-arm

/test ocp-full-conformance-rhel-eus

/test ocp-full-conformance-serial-rhel-eus

/test test-rpm

/test test-unit

/test verify

/test verify-deps

The following commands are available to trigger optional jobs:

/test images

/test security

/test test-rebase

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-microshift-main-e2e-aws-tests

pull-ci-openshift-microshift-main-e2e-aws-tests-arm

pull-ci-openshift-microshift-main-e2e-aws-tests-bootc

pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-arm

pull-ci-openshift-microshift-main-images

pull-ci-openshift-microshift-main-security

pull-ci-openshift-microshift-main-test-rebase

pull-ci-openshift-microshift-main-test-unit

pull-ci-openshift-microshift-main-verify

pull-ci-openshift-microshift-main-verify-deps

Details

In response to this:

/test ?

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash

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:

• OWNERS [ggiguash]

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

[ggiguash]

/test test-rebase

[ggiguash]

/test e2e-aws-tests
/test e2e-aws-tests-arm
/test e2e-aws-tests-bootc
/test e2e-aws-tests-bootc-arm

[ggiguash]

/test verify

[ggiguash]

Failed prometheus image pull with retries.
/test e2e-aws-tests-bootc

[ggiguash]

/test e2e-aws-tests-bootc e2e-aws-tests

[pmtk]

Have you tested the changes in the offline env?

There's assets/optional/cert-manager/manager/images.yaml file which contains references to images I think are manifest lists.
I think we might need to create versions of images.yaml for each arch and include correct one when building an RPM - something like we have for OLM (and other optional pkgs):

microshift/packaging/rpm/microshift.spec

Lines 413 to 419 in ce1759e

	%ifarch %{arm} aarch64
	cat assets/optional/operator-lifecycle-manager/kustomization.aarch64.yaml >> %{buildroot}/%{_prefix}/lib/microshift/manifests.d/001-microshift-olm/kustomization.yaml
	%endif
	%ifarch x86_64
	cat assets/optional/operator-lifecycle-manager/kustomization.x86_64.yaml >> %{buildroot}/%{_prefix}/lib/microshift/manifests.d/001-microshift-olm/kustomization.yaml
	%endif

Edit: what I mean by all this is, even if we package correct refs for mirroring/embedding for disconnected env, if the yaml has multiarch manifest digest, it'll attempt to pull that in order to get ref for its specific architecture.

[ggiguash]

/test all

[openshift-ci]

@ggiguash: 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-aws-tests-bootc	0c7dd01	link	true	/test e2e-aws-tests-bootc
ci/prow/e2e-aws-tests-arm	0c7dd01	link	true	/test e2e-aws-tests-arm
ci/prow/e2e-aws-tests	0c7dd01	link	true	/test e2e-aws-tests

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.