Skip to content

[release-4.22]AGENT-1549: Backport NoRegistryClusterInstall feature to release-4.22#31406

Merged
openshift-merge-bot[bot] merged 7 commits into
openshift:release-4.22from
pawanpinjarkar:422backport
Jul 23, 2026
Merged

[release-4.22]AGENT-1549: Backport NoRegistryClusterInstall feature to release-4.22#31406
openshift-merge-bot[bot] merged 7 commits into
openshift:release-4.22from
pawanpinjarkar:422backport

Conversation

@pawanpinjarkar

@pawanpinjarkar pawanpinjarkar commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

This patch is part of the NoRegistryClusterInstall feature backport to 4.22. It contains the following PR:

#31179
#31250
#31275
#31366
#31394
#31401

This patch updates the openshift/client-go dependency to 0.0.0-20260720094807-fbc45213df28 and openshift/api dependency to v0.0.0-20260717133910-57eb58a15422 to include the InternalReleaseImage v1 resource related to #31294

This is part of the 4.22 IRI backport epic https://redhat.atlassian.net/browse/AGENT-1500

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 20, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 20, 2026

Copy link
Copy Markdown

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

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This patch is part of the NoRegistryClusterInstall feature backport to 4.22. It contains the following PR:

#31179
#31366
#31394
#31275
#31250
#31294

This patch updates the openshift/client-go dependency to 0.0.0-20260720094807-fbc45213df28 and openshift/api dependency to v0.0.0-20260717133910-57eb58a15422 to include the InternalReleaseImage v1 resource.

This is part of the 4.22 IRI backport epic https://redhat.atlassian.net/browse/AGENT-1500

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

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

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: f3e5ded8-1c04-4136-a4c4-cadf6590cd4b

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.

@openshift-ci
openshift-ci Bot requested review from p0lyn0mial and rwsu July 20, 2026 22:25
@openshift-ci openshift-ci Bot added the vendor-update Touching vendor dir or related files label Jul 20, 2026
@pawanpinjarkar pawanpinjarkar changed the title AGENT-1549: Backport NoRegistryClusterInstall feature to release-4.22 [release-4.22]AGENT-1549: Backport NoRegistryClusterInstall feature to release-4.22 Jul 20, 2026
@bfournie

Copy link
Copy Markdown
Contributor

Need to include #31401 after it merges

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/hold for #31401

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 20, 2026
@neisw

neisw commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

/approve

@neisw

neisw commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

/pipeline required

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 21, 2026
@pawanpinjarkar
pawanpinjarkar force-pushed the 422backport branch 2 times, most recently from bffd47d to 4681cc6 Compare July 21, 2026 18:50
@openshift-ci openshift-ci Bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 21, 2026
…p-tests

AGENT-1517: refactored the logic to filter IRI related MachineConfigs
AGENT-1527: Fix comparison of InternalReleaseImage to mirror
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 21, 2026
openshift-merge-bot Bot and others added 5 commits July 21, 2026 15:01
…e-check

AGENT-1535: Increase the time checking for IRI SCC uid-range
OCPBUGS-97603: Use framework-managed namespace for workload test
OCPBUGS-98956: use admin-client namespace creation for IRI workload test
…ollowup

OCPBUGS-99166: wait for default ServiceAccount before creating IRI test pod
…20094807-fbc45213df28 and openshift/api dependency to v0.0.0-20260717133910-57eb58a15422 to include the InternalReleaseImage v1 resource.
@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/hold cancel

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 21, 2026
@openshift-ci

openshift-ci Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

@pawanpinjarkar: The label(s) backport-risk-assessed cannot be applied or removed, because you are not in one of the allowed teams and are not an allowed user. Must be a member of one of these teams: openshift-patch-managers, openshift-release-oversight, openshift-staff-engineers, openshift-sustaining-engineers

Details

In response to this:

/label backport-risk-assessed

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.

@zaneb

zaneb commented Jul 21, 2026

Copy link
Copy Markdown
Member

/label backport-risk-assessed
Manually adding valid-bug 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 Jul 21, 2026
@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 Jul 21, 2026
@bfournie

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 21, 2026
@openshift-ci

openshift-ci Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bfournie, neisw, 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

@smg247

smg247 commented Jul 22, 2026

Copy link
Copy Markdown
Member

/pipeline required

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/test e2e-agent-compact-ipv4-iso-no-registry

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/retest-required

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/verified later by @pawanpinjarkar

@openshift-ci-robot

Copy link
Copy Markdown

@pawanpinjarkar: Only users can be targets for the /verified later command.

Details

In response to this:

/verified later by @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.

@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 Jul 23, 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.

@openshift-ci

openshift-ci Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

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

@openshift-merge-bot
openshift-merge-bot Bot merged commit a023df0 into openshift:release-4.22 Jul 23, 2026
20 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. vendor-update Touching vendor dir or related files 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.