Skip to content

[release-4.22] AGENT-1571: Backport NoRegistryClusterInstall feature cleanup post feature promotion - Remove feature gate - #6417

Open
pawanpinjarkar wants to merge 2 commits into
openshift:release-4.22from
pawanpinjarkar:remove-fg-iri-4.22
Open

[release-4.22] AGENT-1571: Backport NoRegistryClusterInstall feature cleanup post feature promotion - Remove feature gate#6417
pawanpinjarkar wants to merge 2 commits into
openshift:release-4.22from
pawanpinjarkar:remove-fg-iri-4.22

Conversation

@pawanpinjarkar

Copy link
Copy Markdown
Contributor

- What I did

This patch is part of the NoRegistryClusterInstall feature cleanup post feature promotion and backport to 4.22. It contains the following PR:
#6396

- How to verify it

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

- Description for the changelog

The InternalReleaseImage(IRI) functionality will now be always active instead of being gated behind a feature flag
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

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

openshift-ci-robot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

@pawanpinjarkar: This pull request references AGENT-1571 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:

- What I did

This patch is part of the NoRegistryClusterInstall feature cleanup post feature promotion and backport to 4.22. It contains the following PR:
#6396

- How to verify it

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

- Description for the changelog

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

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

@coderabbitai

coderabbitai Bot commented Aug 18, 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: caede093-1b2a-4fee-a1c9-c459e3fcc678

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.

@openshift-ci
openshift-ci Bot requested review from bfournie and djoshy August 18, 2026 14:49
@pawanpinjarkar pawanpinjarkar changed the title [release-4.22] AGENT-1571: Backport NoRegistryClusterInstall feature cleanup post feature promotion [release-4.22] AGENT-1571: Backport NoRegistryClusterInstall feature cleanup post feature promotion - Remove feature gate Aug 18, 2026
@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

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

@bfournie

Copy link
Copy Markdown
Contributor

/retest-required

@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 Aug 18, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-upgrade
/test e2e-gcp-op-ocl-part1
/test e2e-gcp-op-ocl-part2
/test e2e-gcp-op-part1
/test e2e-gcp-op-part2
/test e2e-gcp-op-single-node
/test e2e-hypershift

@openshift-ci

openshift-ci Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bfournie, pawanpinjarkar
Once this PR has been reviewed and has the lgtm label, please assign rishabhsaini 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:

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

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

@openshift-ci

openshift-ci Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

@pawanpinjarkar: 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-gcp-op-single-node 664e9d2 link true /test e2e-gcp-op-single-node
ci/prow/e2e-gcp-op-part1 664e9d2 link true /test e2e-gcp-op-part1

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants