Skip to content

AGENT-1522: bump InternalReleaseImage to v1#31294

Open
pawanpinjarkar wants to merge 1 commit into
openshift:mainfrom
pawanpinjarkar:promote-iri-api-2-v1
Open

AGENT-1522: bump InternalReleaseImage to v1#31294
pawanpinjarkar wants to merge 1 commit into
openshift:mainfrom
pawanpinjarkar:promote-iri-api-2-v1

Conversation

@pawanpinjarkar

@pawanpinjarkar pawanpinjarkar commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

Summary by CodeRabbit

  • Chores

    • Updated Go module dependencies to newer versions.
  • Tests

    • Migrated InternalReleaseImage test helper operations and availability checks from legacy v1alpha1 APIs to stable v1.
    • Extended the config v1 client shim to support CRIO credential provider configuration resources.

Requires

@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: automatic 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 Jun 11, 2026
@openshift-ci-robot

openshift-ci-robot commented Jun 11, 2026

Copy link
Copy Markdown

@pawanpinjarkar: This pull request references AGENT-1522 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 "5.0.0" version, but no target version was set.

Details

In response to this:

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 Jun 11, 2026

Copy link
Copy Markdown

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

Updates Go module versions, migrates InternalReleaseImage test helpers from MachineConfig v1alpha1 to stable v1, and adds a ConfigV1 shim accessor for CRIO credential provider configs.

Changes

Dependency and client updates

Layer / File(s) Summary
Module requirement updates
go.mod
Refreshes OpenShift, Kubernetes, golang.org/x, go-openapi, and indirect module requirements, including removal of two indirect modules.
InternalReleaseImage v1 migration
test/extended/internalreleaseimage/helper.go
Uses the stable MachineConfig v1 client for InternalReleaseImage initialization, retrieval, deletion, and availability probing.
CRIO credential provider shim
test/extended/util/configv1shim.go
Adds CRIOCredentialProviderConfigs() with the existing static-kind guard and delegated client call.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Suggested reviewers: sjenning, p0lyn0mial

🚥 Pre-merge checks | ✅ 13 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Test Structure And Quality ⚠️ Warning FAIL: The new project e2e specs are monolithic and add many bare Expect(err).NotTo(HaveOccurred()) assertions without diagnostic messages, violating the test-quality checklist. Split the scenarios into smaller It blocks and add descriptive failure messages to resource creation/wait assertions, especially in project.go.
Single Node Openshift (Sno) Test Compatibility ⚠️ Warning image_mirror_set.go creates a custom MCP from a worker node and only skips MicroShift; there’s no SNO guard, and SNO/compact nodes can’t join custom MCPs. Add a SNO guard (SkipIfNotTopology(...SingleReplicaTopologyMode)/IsSingleNode) or mark the mirror-set test [Skipped:SingleReplicaTopology].
✅ Passed checks (13 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main change: migrating InternalReleaseImage to v1.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed No changed Ginkgo titles include dynamic data; all test names are static strings, and the only generated values are used in test bodies.
Microshift Test Compatibility ✅ Passed No new Ginkgo tests were added; touched internalreleaseimage tests already carry [apigroup:machineconfiguration.openshift.io] and are skipped on MicroShift.
Topology-Aware Scheduling Compatibility ✅ Passed No manifests/controllers were added, and the diff has no new anti-affinity, topology spread, or control-plane selectors; only a worker-node lookup in a test helper.
Ote Binary Stdout Contract ✅ Passed Touched files only update helper/shim logic; no main/init/TestMain/suite setup or stdout writes were added.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Added e2e tests only check cluster config or use cluster-mapped images/routes; I found no new IPv4-only logic or external internet dependency in the PR delta.
No-Weak-Crypto ✅ Passed No new weak-crypto code or secret comparisons were added; the only hits were incidental in generated docs/vendor metadata, not in added code lines.
Container-Privileges ✅ Passed No privileged/host* or allowPrivilegeEscalation settings were added; the new pod spec uses restricted security contexts and the devcontainer runs as vscode.
No-Sensitive-Data-In-Logs ✅ Passed The PR adds no new log statements or sensitive-value printing; touched code only migrates clients and adds a shim method.
✨ 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 added the vendor-update Touching vendor dir or related files label Jun 11, 2026
@openshift-ci
openshift-ci Bot requested review from p0lyn0mial and sjenning June 11, 2026 19:51

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@go.mod`:
- Line 469: The go.mod currently replaces github.com/openshift/api with a
personal fork (github.com/pawanpinjarkar/api v0.0.0-...) — remove or justify
this replace entry: either revert the replace to a vetted upstream tagged
release or, if the fork is required, add a PR rationale and approval trail in
the PR description referencing the replace line and module name, document
whether this is temporary or permanent, and include provenance evidence
(SBOM/signing/cosign or sigstore attestations), license compatibility and
CVE/osv.dev checks for that specific pseudo-version, and a compatibility
statement confirming no API-breaking changes for
github.com/openshift/api/config/*; block production usage until these
checks/approvals are added or remove the replace and use an officially governed
source.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 1cf63daf-600b-42d4-bc1d-3ec6217ec934

📥 Commits

Reviewing files that changed from the base of the PR and between bde16f5 and 6189ba6.

⛔ Files ignored due to path filters (17)
  • go.sum is excluded by !**/*.sum
  • vendor/github.com/openshift/api/.ci-operator.yaml is excluded by !**/vendor/**, !vendor/**
  • vendor/github.com/openshift/api/Dockerfile.ocp is excluded by !**/vendor/**, !vendor/**
  • vendor/github.com/openshift/api/config/v1alpha1/types_cluster_monitoring.go is excluded by !**/vendor/**, !vendor/**
  • vendor/github.com/openshift/api/config/v1alpha1/zz_generated.deepcopy.go is excluded by !**/vendor/**, !vendor/**, !**/zz_generated*
  • vendor/github.com/openshift/api/config/v1alpha1/zz_generated.swagger_doc_generated.go is excluded by !**/vendor/**, !vendor/**, !**/zz_generated*
  • vendor/github.com/openshift/api/features.md is excluded by !**/vendor/**, !vendor/**
  • vendor/github.com/openshift/api/features/features.go is excluded by !**/vendor/**, !vendor/**
  • vendor/github.com/openshift/api/machineconfiguration/v1/register.go is excluded by !**/vendor/**, !vendor/**
  • vendor/github.com/openshift/api/machineconfiguration/v1/types.go is excluded by !**/vendor/**, !vendor/**
  • vendor/github.com/openshift/api/machineconfiguration/v1/types_internalreleaseimage.go is excluded by !**/vendor/**, !vendor/**
  • vendor/github.com/openshift/api/machineconfiguration/v1/zz_generated.deepcopy.go is excluded by !**/vendor/**, !vendor/**, !**/zz_generated*
  • vendor/github.com/openshift/api/machineconfiguration/v1/zz_generated.featuregated-crd-manifests.yaml is excluded by !**/vendor/**, !vendor/**, !**/zz_generated*
  • vendor/github.com/openshift/api/machineconfiguration/v1/zz_generated.swagger_doc_generated.go is excluded by !**/vendor/**, !vendor/**, !**/zz_generated*
  • vendor/github.com/openshift/api/operator/v1/types_etcd.go is excluded by !**/vendor/**, !vendor/**
  • vendor/github.com/openshift/api/operator/v1/zz_generated.swagger_doc_generated.go is excluded by !**/vendor/**, !vendor/**, !**/zz_generated*
  • vendor/modules.txt is excluded by !**/vendor/**, !vendor/**
📒 Files selected for processing (1)
  • go.mod

Comment thread go.mod Outdated
@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/payload-job-with-prs periodic-ci-openshift-release-main-nightly-5.0-e2e-agent-compact-iso-no-registry-techpreview openshift/api#2880

@openshift-ci

openshift-ci Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

@pawanpinjarkar: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/payload-job-with-prs periodic-ci-openshift-release-main-nightly-5.0-e2e-agent-compact-iso-no-registry-techpreview openshift/api#2880

@openshift-ci

openshift-ci Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

@pawanpinjarkar: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/payload-job-with-prs ?

@openshift-ci

openshift-ci Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

@pawanpinjarkar: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
test/extended/internalreleaseimage/helper.go (1)

51-55: ⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Incomplete v1alpha1 to v1 migration in test/extended/internalreleaseimage/helper.go. Both GetIRI() (Line 52) and DeleteIRI() (Line 88) still reference the removed h.McClientV1alpha1 field instead of h.McClientV1. The correct v1 migration pattern is shown on Line 244. These references will cause compilation errors.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@test/extended/internalreleaseimage/helper.go` around lines 51 - 55, GetIRI()
and DeleteIRI() still use the removed h.McClientV1alpha1 client and will not
compile; update both functions to use h.McClientV1 instead (i.e., replace
references to h.McClientV1alpha1.InternalReleaseImages() with
h.McClientV1.InternalReleaseImages()) and keep the existing calls to
Get(context.Background(), IRIResourceName, metav1.GetOptions{}) and
Delete(context.Background(), IRIResourceName, metav1.DeleteOptions{}) unchanged
so they follow the v1 migration pattern used elsewhere (see the pattern around
the other v1 usage).
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@test/extended/internalreleaseimage/helper.go`:
- Around line 51-55: GetIRI() and DeleteIRI() still use the removed
h.McClientV1alpha1 client and will not compile; update both functions to use
h.McClientV1 instead (i.e., replace references to
h.McClientV1alpha1.InternalReleaseImages() with
h.McClientV1.InternalReleaseImages()) and keep the existing calls to
Get(context.Background(), IRIResourceName, metav1.GetOptions{}) and
Delete(context.Background(), IRIResourceName, metav1.DeleteOptions{}) unchanged
so they follow the v1 migration pattern used elsewhere (see the pattern around
the other v1 usage).

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: dad0f1c4-b0f9-4a6e-8d82-85157cc6056e

📥 Commits

Reviewing files that changed from the base of the PR and between 6189ba6 and 00d544f.

📒 Files selected for processing (1)
  • test/extended/internalreleaseimage/helper.go

@openshift-ci openshift-ci Bot added the ready-for-human-review Indicates a PR has been reviewed by automated tools and is ready for human review label Jun 11, 2026
@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/payload-job-with-prs periodic-ci-openshift-release-main-nightly-5.0-e2e-agent-compact-iso-no-registry-techpreview openshift/api#2880 openshift/client-go#383

@openshift-ci

openshift-ci Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

@pawanpinjarkar: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

@pawanpinjarkar
pawanpinjarkar force-pushed the promote-iri-api-2-v1 branch from 4437a1b to 552a5e8 Compare July 6, 2026 14:56
@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

/retest-required

2 similar comments
@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/retest-required

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/retest-required

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/payload-job-with-prs periodic-ci-openshift-release-main-nightly-5.0-e2e-agent-compact-iso-no-registry-techpreview

@openshift-ci

openshift-ci Bot commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

@pawanpinjarkar: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-ovn-fips

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/retest-required

@sadasu

sadasu commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

/test e2e-aws-ovn-fips

@openshift-ci openshift-ci Bot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Jul 15, 2026
@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/test ?

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

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

@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

@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 16, 2026
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 16, 2026
@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

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

@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 16, 2026
@openshift-ci

openshift-ci Bot commented Jul 16, 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 jogeo 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

@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

1 similar comment
@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

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

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 17, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@pawanpinjarkar: This PR has been marked as verified by [ci/prow/e2e-agent-compact-ipv4-iso-no-registry](https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/31294/pull-ci-openshift-origin-main-e2e-agent-compact-ipv4-iso-no-registry/2078112253671903232).

Details

In response to this:

/verified by ci/prow/e2e-agent-compact-ipv4-iso-no-registry

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

/retest-required

2 similar comments
@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/retest-required

@pawanpinjarkar

Copy link
Copy Markdown
Contributor Author

/retest-required

@openshift-ci

openshift-ci Bot commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

@pawanpinjarkar: The following test 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-ovn b1f40d1 link true /test e2e-gcp-ovn

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. ready-for-human-review Indicates a PR has been reviewed by automated tools and is ready for human review vendor-update Touching vendor dir or related files verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants