Skip to content

AGENT-1431: Backport feature NoRegistryClusterInstall to 4.21#248

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.21from
pawanpinjarkar:cherrypick-AGENT-1313-enable-MCO-IRI-registry
Feb 8, 2026
Merged

AGENT-1431: Backport feature NoRegistryClusterInstall to 4.21#248
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.21from
pawanpinjarkar:cherrypick-AGENT-1313-enable-MCO-IRI-registry

Conversation

@pawanpinjarkar
Copy link
Copy Markdown
Contributor

Manual changes as per AGENT-1313: enable MCO IRI registry #232

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 5, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Feb 5, 2026

@pawanpinjarkar: This pull request references AGENT-1431 which is a valid jira issue.

Details

In response to this:

Manual changes as per AGENT-1313: enable MCO IRI registry #232

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 andfasano and bfournie February 5, 2026 14:40
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Feb 5, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pawanpinjarkar

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 5, 2026
@bfournie
Copy link
Copy Markdown
Contributor

bfournie commented Feb 5, 2026

/label backport-risk-assessed
/lgtm

@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 5, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Feb 5, 2026
@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/verified later @pawanpinjarkar

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Feb 5, 2026

@pawanpinjarkar: 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.

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/verified later @pawanpinjarkar

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

@pawanpinjarkar: This PR has been marked to be verified later by @pawanpinjarkar.

Details

In response to this:

/verified later @pawanpinjarkar

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.

@zaneb
Copy link
Copy Markdown
Member

zaneb commented Feb 8, 2026

Setting jira/valid-bug manually as this is subject to an approved SBAR.

@zaneb zaneb added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Feb 8, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit f44c7af into openshift:release-4.21 Feb 8, 2026
13 checks passed
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/valid-bug Indicates that a referenced Jira bug is valid 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.

4 participants