CM-1236: Use staged 1.19.2 operator and operand images for CI testing

[mytreya-rh]

Summary

Test-only PR — do not merge.

Points the operator image and RELATED_IMAGE_* env vars at the staged 1.19.2 digests from cert-manager-operator-release images_digest.conf on release-1.19 so operator CI e2e (e2e-operator) runs the staged stack instead of pipeline-substituted quay.io/jetstack / openshift.io/cert-manager-operator images.

ci-operator substitutions only rewrite quay.io/jetstack/... and openshift.io/cert-manager-operator:.*. Using registry.stage.redhat.io/...@sha256:... means those substitutions no longer match. The e2e-operator job already runs merge-stage-registry-credentials, so the cluster can pull from registry.stage.redhat.io.

Jira: https://redhat.atlassian.net/browse/CM-1236

Image mapping

Component	Pullspec
Operator	registry.stage.redhat.io/cert-manager/cert-manager-operator-rhel9@sha256:ebb988080e93a733111f641cda75c30fb773509e9e35d928fe41262871d0fa68
webhook / cainjector / controller	registry.stage.redhat.io/cert-manager/jetstack-cert-manager-rhel9@sha256:9144fd826b65687970a6a88a4e7e50cc9b4bf4b76d3c427f1de6899e6a79b7fa
acmesolver	registry.stage.redhat.io/cert-manager/jetstack-cert-manager-acmesolver-rhel9@sha256:5e42c5983bf93e3d0f31de628dc7d96ceec6136cdcb5f9e22dd29cc5193951a0
istio-csr	registry.stage.redhat.io/cert-manager/cert-manager-istio-csr-rhel9@sha256:ed4f77362a05546f5809ae3675f5c5e8093453e7785f580f93348419900c1f06
trust-manager	registry.stage.redhat.io/cert-manager/cert-manager-trust-manager-rhel9@sha256:d0834b140e53cb2b96d30f227b0c7dcab3463eeab80049df608582c45c792a82

The operator is pinned on config/manager/manager.yaml image: (replacing controller:latest), not via kustomization.yaml. make bundle always runs kustomize edit set image controller=openshift.io/cert-manager-operator:latest; pinning only in kustomize would be reset and ci-operator would inject the PR-built operator again.

The CSV is regenerated with make bundle so hack/verify-bundle.sh stays green. spec.relatedImages collapses webhook/cainjector/controller to one entry because they share a digest (operator-sdk warning); the RELATED_IMAGE_* env vars still list each component separately, which is what the operator uses at runtime.

Test plan

• Confirm e2e-operator runs (not skipped)
• Operator pod uses registry.stage.redhat.io/cert-manager/cert-manager-operator-rhel9@sha256:ebb98808...
• Operand deployments use the staged jetstack / acmesolver / istio-csr / trust-manager digests
• No ImagePullBackOff (stage credentials merged into the cluster pull secret)
• Close this PR without merging after CI results are collected

Always review AI generated responses prior to use.
Generated with Claude Code via openshift-developer plugin

Made with Cursor

[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]

@mytreya-rh: This pull request references CM-1236 which is a valid jira issue.

Details

In response to this:

Summary

Test-only PR — do not merge.

Points the operator image and RELATED_IMAGE_* env vars at the staged 1.19.2 digests from cert-manager-operator-release images_digest.conf on release-1.19 so operator CI e2e (e2e-operator) runs the staged stack instead of pipeline-substituted quay.io/jetstack / openshift.io/cert-manager-operator images.

ci-operator substitutions only rewrite quay.io/jetstack/... and openshift.io/cert-manager-operator:.*. Using registry.stage.redhat.io/...@sha256:... means those substitutions no longer match. The e2e-operator job already runs merge-stage-registry-credentials, so the cluster can pull from registry.stage.redhat.io.

Jira: https://redhat.atlassian.net/browse/CM-1236

Image mapping

Component	Pullspec
Operator	registry.stage.redhat.io/cert-manager/cert-manager-operator-rhel9@sha256:ebb988080e93a733111f641cda75c30fb773509e9e35d928fe41262871d0fa68
webhook / cainjector / controller	registry.stage.redhat.io/cert-manager/jetstack-cert-manager-rhel9@sha256:9144fd826b65687970a6a88a4e7e50cc9b4bf4b76d3c427f1de6899e6a79b7fa
acmesolver	registry.stage.redhat.io/cert-manager/jetstack-cert-manager-acmesolver-rhel9@sha256:5e42c5983bf93e3d0f31de628dc7d96ceec6136cdcb5f9e22dd29cc5193951a0
istio-csr	registry.stage.redhat.io/cert-manager/cert-manager-istio-csr-rhel9@sha256:ed4f77362a05546f5809ae3675f5c5e8093453e7785f580f93348419900c1f06
trust-manager	registry.stage.redhat.io/cert-manager/cert-manager-trust-manager-rhel9@sha256:d0834b140e53cb2b96d30f227b0c7dcab3463eeab80049df608582c45c792a82

The operator is pinned on config/manager/manager.yaml image: (replacing controller:latest), not via kustomization.yaml. make bundle always runs kustomize edit set image controller=openshift.io/cert-manager-operator:latest; pinning only in kustomize would be reset and ci-operator would inject the PR-built operator again.

The CSV is regenerated with make bundle so hack/verify-bundle.sh stays green. spec.relatedImages collapses webhook/cainjector/controller to one entry because they share a digest (operator-sdk warning); the RELATED_IMAGE_* env vars still list each component separately, which is what the operator uses at runtime.

Test plan

• Confirm e2e-operator runs (not skipped)
• Operator pod uses registry.stage.redhat.io/cert-manager/cert-manager-operator-rhel9@sha256:ebb98808...
• Operand deployments use the staged jetstack / acmesolver / istio-csr / trust-manager digests
• No ImagePullBackOff (stage credentials merged into the cluster pull secret)
• Close this PR without merging after CI results are collected

Always review AI generated responses prior to use.
Generated with Claude Code via openshift-developer plugin

Made with Cursor

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mytreya-rh

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 [mytreya-rh]

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

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: a5211b53-5010-4d82-a349-f0e1df789860

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[mytreya-rh]

/test e2e-operator-aws-proxy
/test e2e-operator-aws-upi-proxy
/test e2e-operator-aws-sts
/test e2e-operator-gcp-ovn
/test e2e-operator-gcp-workload-identity
/test e2e-operator-azure-ovn
/test e2e-operator-azure-workload-identity
/test e2e-operator-consoleless

[mytreya-rh]

/test e2e-operator
/test e2e-operator-tech-preview

[openshift-ci]

@mytreya-rh: all tests passed!

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.