Skip to content

Conversation

@alebedev87
Copy link
Contributor

@alebedev87 alebedev87 commented Jan 20, 2025

  • Upgraded k8s.io/api, k8s.io/apiextensions-apiserver, and k8s.io/client-go to v0.32.1.
  • Updated sigs.k8s.io/controller-runtime to v0.20.1 (compatible with k8s v0.32).
  • Go version was implicitly bumped to 1.23.0 as part of the dependency updates.

Commands used for the upgrade:

go get k8s.io/[email protected]
go get k8s.io/[email protected]
go mod edit -replace k8s.io/client-go=k8s.io/[email protected]
go get sigs.k8s.io/[email protected]
go mod tidy
go mod vendor

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 20, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 20, 2025

@alebedev87: This pull request references NE-1936 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.19.0" version, but no target version was set.

In response to this:

  • Upgraded k8s.io/api, k8s.io/apiextensions-apiserver, and k8s.io/client-go to v0.32.1.
  • Updated sigs.k8s.io/controller-runtime to v0.20.0 (compatible with k8s v0.32).
  • Go version was implicitly bumped to 1.23.0 as part of the dependency updates.

Commands used for the upgrade:

   go get k8s.io/[email protected]
   go get k8s.io/[email protected]
   go mod edit -replace k8s.io/client-go=k8s.io/[email protected]
   go get sigs.k8s.io/[email protected]
   go mod tidy
   go mod vendor

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 gcs278 and miheer January 20, 2025 21:51
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 20, 2025

@alebedev87: This pull request references NE-1936 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.19.0" version, but no target version was set.

In response to this:

  • Upgraded k8s.io/api, k8s.io/apiextensions-apiserver, and k8s.io/client-go to v0.32.1.
  • Updated sigs.k8s.io/controller-runtime to v0.20.0 (compatible with k8s v0.32).
  • Go version was implicitly bumped to 1.23.0 as part of the dependency updates.

Commands used for the upgrade:

go get k8s.io/[email protected]
go get k8s.io/[email protected]
go mod edit -replace k8s.io/client-go=k8s.io/[email protected]
go get sigs.k8s.io/[email protected]
go mod tidy
go mod vendor

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.

@alebedev87
Copy link
Contributor Author

/retest

1 similar comment
@alebedev87
Copy link
Contributor Author

/retest

@Miciah
Copy link
Contributor

Miciah commented Jan 22, 2025

/assign

@alebedev87
Copy link
Contributor Author

openshift/origin#29466 is supposed to fix e2e-aws-ocn-serial.

go.mod Outdated
k8s.io/utils v0.0.0-20240711033017-18e509b52bc8
sigs.k8s.io/controller-runtime v0.19.0
k8s.io/utils v0.0.0-20241104100929-3ea5e8cea738
sigs.k8s.io/controller-runtime v0.20.0
Copy link
Contributor

@gcs278 gcs278 Jan 23, 2025

Choose a reason for hiding this comment

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

0.20.1 is out (that was quick). I see two fixes (kubernetes-sigs/controller-runtime#3079 and kubernetes-sigs/controller-runtime#3086) that might be of interest. Up to you if you want to bump again.

https://github.com/kubernetes-sigs/controller-runtime/releases/tag/v0.20.1

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right, I saw they dropped a new one. Let me add it.

@alebedev87 alebedev87 force-pushed the ne-1936-bump-k8s-1-32 branch from bdcd59b to ff1f469 Compare January 24, 2025 16:55
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 24, 2025
- Upgraded k8s.io/api, k8s.io/apiextensions-apiserver, and k8s.io/client-go to v0.32.1.
- Updated sigs.k8s.io/controller-runtime to v0.20.1 (compatible with k8s v0.32).
- Go version was implicitly bumped to 1.23.0 as part of the dependency updates.

Commands used for the upgrade:
    go get k8s.io/[email protected]
    go get k8s.io/[email protected]
    go mod edit -replace k8s.io/client-go=k8s.io/[email protected]
    go get sigs.k8s.io/[email protected]
    go mod tidy
    go mod vendor
@alebedev87 alebedev87 force-pushed the ne-1936-bump-k8s-1-32 branch from ff1f469 to 6ed63fe Compare January 24, 2025 16:58
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 24, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 24, 2025

@alebedev87: This pull request references NE-1936 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.19.0" version, but no target version was set.

In response to this:

  • Upgraded k8s.io/api, k8s.io/apiextensions-apiserver, and k8s.io/client-go to v0.32.1.
  • Updated sigs.k8s.io/controller-runtime to v0.20.1 (compatible with k8s v0.32).
  • Go version was implicitly bumped to 1.23.0 as part of the dependency updates.

Commands used for the upgrade:

go get k8s.io/[email protected]
go get k8s.io/[email protected]
go mod edit -replace k8s.io/client-go=k8s.io/[email protected]
go get sigs.k8s.io/[email protected]
go mod tidy
go mod vendor

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.

@alebedev87
Copy link
Contributor Author

/retest

@candita
Copy link
Contributor

candita commented Feb 26, 2025

/cc @shaneutt

@openshift-ci openshift-ci bot requested a review from shaneutt February 26, 2025 22:36
@knobunc
Copy link

knobunc commented Mar 3, 2025

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: knobunc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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

@knobunc
Copy link

knobunc commented Mar 3, 2025

/lgtm

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 3, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2025
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 26f8b0f and 2 for PR HEAD 6ed63fe in total

@Miciah
Copy link
Contributor

Miciah commented Mar 3, 2025

e2e-gcp-operator failed because TestConnectTimeout and TestUnmanagedDNSToManagedDNSIngressController failed:

=== NAME  TestAll/parallel/TestConnectTimeout
    operator_test.go:3321: got unexpected error while sending request: Get "http://34.136.99.34": dial tcp 34.136.99.34:80: i/o timeout
    operator_test.go:3349: failed to observe expected condition: context deadline exceeded
=== NAME  TestAll/parallel/TestConnectTimeout
    operator_test.go:3234: deleted ingresscontroller test-connect-timeout

=== NAME  TestAll/parallel/TestUnmanagedDNSToManagedDNSIngressController
    util_test.go:109: retrying client call due to: Get "http://34.29.34.185": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
    unmanaged_dns_test.go:74: failed to verify connectivity with workload with reqURL http://34.29.34.185 using external client: timed out waiting for the condition

Looks like infrastructure issues.

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 26f8b0f and 2 for PR HEAD 6ed63fe in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 4, 2025

@alebedev87: all tests passed!

Full PR test history. Your PR dashboard.

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 69cadab into openshift:master Mar 4, 2025
19 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-ingress-operator
This PR has been included in build ose-cluster-ingress-operator-container-v4.19.0-202503040641.p0.g69cadab.assembly.stream.el9.
All builds following this will include this PR.

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

8 participants