NE-2730: Switch container digests to stage registry for 1.2.2 release

[Thealisyed]

Summary

• Switch operator and operand pullspecs in container_digest.sh from registry.redhat.io to registry.stage.redhat.io
• Digests remain the same as the nudging PRs (NE-2730: Update external-dns-operator-container-ext-dns-optr-1-2-rhel-8 to cb6bdce #449, NE-2730: Update external-dns-container-ext-dns-optr-1-2-rhel-8 to 4904997 #456)
• Required for the stage release pipeline to pass the Conforma test (ref: release process doc)

Context

Per the Konflux release process:

In order for the stage release pipeline to pass the Conforma test, the registry/repository in bundle-hack/container_digest.sh must be set to registry.stage.redhat.io/edo/*. Keep the digests the same as the ones created by the nudging PR.

Note

After stage release is verified, a follow-up PR will swap back to registry.redhat.io for the production release.

[openshift-ci-robot]

@Thealisyed: This pull request references NE-2730 which is a valid jira issue.

Details

In response to this:

Summary

• Switch operator and operand pullspecs in container_digest.sh from registry.redhat.io to registry.stage.redhat.io
• Digests remain the same as the nudging PRs (NE-2730: Update external-dns-operator-container-ext-dns-optr-1-2-rhel-8 to cb6bdce #449, NE-2730: Update external-dns-container-ext-dns-optr-1-2-rhel-8 to 4904997 #456)
• Required for the stage release pipeline to pass the Conforma test (ref: release process doc)

Context

Per the Konflux release process:

In order for the stage release pipeline to pass the Conforma test, the registry/repository in bundle-hack/container_digest.sh must be set to registry.stage.redhat.io/edo/*. Keep the digests the same as the ones created by the nudging PR.

Note

After stage release is verified, a follow-up PR will swap back to registry.redhat.io for the production release.

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.

[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: cba375b3-151c-4696-b0a2-0952075776c5

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign knobunc for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[Thealisyed]

/close
In favor of #477, Andrey's PR adds registry.redhat.io/edo/* mirrors to the deploy pipeline, allowing the bundle to reference the prod registry from the start.
This eliminates the need to swap to registry.stage.redhat.io and back thereby saving two steps in the release process.

[openshift-ci]

@Thealisyed: Closed this PR.

Details

In response to this:

/close
In favor of #477, Andrey's PR adds registry.redhat.io/edo/* mirrors to the deploy pipeline, allowing the bundle to reference the prod registry from the start.
This eliminates the need to swap to registry.stage.redhat.io and back thereby saving two steps in the release process.

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.