Skip to content

[release-4.19] OCPBUGS-88355: sync deps for release-4.19 and go build image tags with ART build - #209

Open
sunku5494 wants to merge 5 commits into
openshift:release-4.19from
sunku5494:sync-deps-gobuild-4.19
Open

[release-4.19] OCPBUGS-88355: sync deps for release-4.19 and go build image tags with ART build#209
sunku5494 wants to merge 5 commits into
openshift:release-4.19from
sunku5494:sync-deps-gobuild-4.19

Conversation

@sunku5494

@sunku5494 sunku5494 commented Jun 10, 2026

Copy link
Copy Markdown

sync deps and build images for release-4.19

  - Bump Go version from 1.22 to 1.23
  - Bump Kubernetes deps from 1.31.1 to 1.32.1
  - Update OpenShift deps to release-4.19 branches
  - Update kubernetes-apiserver fork to openshift-apiserver-4.19-kubernetes-1.32.1
  - Adapt to Go 1.23 API changes: PostStartHookContext.StopCh replaced
    with embedded context.Context, unexported fake client types,
    utilversion moved to k8s.io/component-base/version
  - Update CI build images and Dockerfile

  - Bump Go version from 1.22 to 1.23
  - Bump Kubernetes deps from 1.31.1 to 1.32.1
  - Update OpenShift deps to release-4.19 branches
  - Update kubernetes-apiserver fork to openshift-apiserver-4.19-kubernetes-1.32.1
  - Adapt to Go 1.23 API changes: PostStartHookContext.StopCh replaced
    with embedded context.Context, unexported fake client types,
    utilversion moved to k8s.io/component-base/version
  - Update CI build images and Dockerfile

Signed-off-by: Venkata Charan Sunku <vsunku@redhat.com>
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 10, 2026
@coderabbitai

coderabbitai Bot commented Jun 10, 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: 201dc0f3-b4f6-4c9c-81fe-e455bd1322ea

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
openshift-ci Bot requested review from benluddy and sanchezl June 10, 2026 17:52
@sunku5494

Copy link
Copy Markdown
Author

/test e2e-component

Signed-off-by: Venkata Charan Sunku <vsunku@redhat.com>
@sunku5494

Copy link
Copy Markdown
Author

/retitle [release-4.19] OCPBUGS-88355: sync deps for release-4.19 and go build image tags with ART build

@openshift-ci openshift-ci Bot changed the title WIP: Sync deps gobuild 4.19 [release-4.19] OCPBUGS-88355: sync deps for release-4.19 and go build image tags with ART build Jun 11, 2026
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 11, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 11, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@sunku5494: This pull request references Jira Issue OCPBUGS-88355, which is invalid:

  • expected Jira Issue OCPBUGS-88355 to depend on a bug targeting a version in 4.20.0, 4.20.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

sync deps and build images for release-4.19

 - Bump Go version from 1.22 to 1.23
 - Bump Kubernetes deps from 1.31.1 to 1.32.1
 - Update OpenShift deps to release-4.19 branches
 - Update kubernetes-apiserver fork to openshift-apiserver-4.19-kubernetes-1.32.1
 - Adapt to Go 1.23 API changes: PostStartHookContext.StopCh replaced
   with embedded context.Context, unexported fake client types,
   utilversion moved to k8s.io/component-base/version
 - Update CI build images and Dockerfile

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.

@sanchezl sanchezl left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Did you mean to check in the _output/ dir?

Comment thread go.mod Outdated
Signed-off-by: Venkata Charan Sunku <vsunku@redhat.com>
@sunku5494
sunku5494 requested a review from sanchezl June 12, 2026 09:20
Signed-off-by: Venkata Charan Sunku <vsunku@redhat.com>
@sunku5494
sunku5494 force-pushed the sync-deps-gobuild-4.19 branch from 0ed2c07 to 10a0cc7 Compare June 12, 2026 10:36
@openshift-ci

openshift-ci Bot commented Jun 12, 2026

Copy link
Copy Markdown

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

@prabhapa

prabhapa commented Jul 7, 2026

Copy link
Copy Markdown

/label jira/skip-dependent-bug-check
as its branch specific

@openshift-ci openshift-ci Bot added the jira/skip-dependent-bug-check Indicates that the referenced Jira bug does not require a dependent bug. label Jul 7, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 7, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@sunku5494: This pull request references Jira Issue OCPBUGS-88355, which is valid. The bug has been moved to the POST state.

4 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.z) matches configured target version for branch (4.19.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
Details

In response to this:

sync deps and build images for release-4.19

 - Bump Go version from 1.22 to 1.23
 - Bump Kubernetes deps from 1.31.1 to 1.32.1
 - Update OpenShift deps to release-4.19 branches
 - Update kubernetes-apiserver fork to openshift-apiserver-4.19-kubernetes-1.32.1
 - Adapt to Go 1.23 API changes: PostStartHookContext.StopCh replaced
   with embedded context.Context, unexported fake client types,
   utilversion moved to k8s.io/component-base/version
 - Update CI build images and Dockerfile

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.

@sanchezl sanchezl left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM — clean dep sync. All k8s 1.32 API adaptations (PostStartHookContext.Done(), utilversion move, unexported fake types, field selector error string) are correct. Previous _output/ concern addressed. CI all green.

/lgtm
/approve

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

openshift-ci Bot commented Jul 7, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sanchezl

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 Jul 7, 2026
@sunku5494

Copy link
Copy Markdown
Author

/verified by CI

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

Copy link
Copy Markdown
Contributor

@sunku5494: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

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. jira/skip-dependent-bug-check Indicates that the referenced Jira bug does not require a dependent bug. 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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants