-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RHOAIENG-8658, RHOAIENG-8651: Update to go 1.21 and apply go mod tidy
changes
#349
RHOAIENG-8658, RHOAIENG-8651: Update to go 1.21 and apply go mod tidy
changes
#349
Conversation
At some point, we will be requested to move to go 1.21. This PR is meant to try it out ahead of time. Looks like there's an OCP-CI change that needs to be done. Something like @atheo89 did in edit: let's just do it rn, |
Related to this PR: * opendatahub-io/kubeflow#349 Update go to version 1.21 to fix the failing tests and ensure consistency across all environments.
Just to be clear - what are motivations for this version bump? |
Yes, go mod tidy, it is like poetry lock, it updates .sum file based on .mod file. We will need it soon. It's those emails about us needing to be on the latest version of go-toolset to get security fixes. I think it is not something urgent for 2.10, but 2.11 it will probably need to be done. |
Related to this PR: * opendatahub-io/kubeflow#349 Update go to version 1.21 to fix the failing tests and ensure consistency across all environments.
Related to this PR: * opendatahub-io/kubeflow#349 Update go to version 1.21 to fix the failing tests and ensure consistency across all environments.
Related to this PR: * opendatahub-io/kubeflow#349 Update go to version 1.21 to fix the failing tests and ensure consistency across all environments.
Related to this PR: * opendatahub-io/kubeflow#349 Update go to version 1.21 to fix the failing tests and ensure consistency across all environments.
Related to this PR: * opendatahub-io/kubeflow#349 Update go to version 1.21 to fix the failing tests and ensure consistency across all environments.
Related to this PR: * opendatahub-io/kubeflow#349 Update go to version 1.21 to fix the failing tests and ensure consistency across all environments. The order of keys in releases.latest.candidate actually matters!
go mod tidy
go mod tidy
changes
Related to this PR: * opendatahub-io/kubeflow#349 Update go to version 1.21 to fix the failing tests and ensure consistency across all environments. CAUTION: The order of keys in releases.latest.candidate actually matters! Inspired by this Dashboard PR * openshift#53354 (review)
go mod tidy
changesgo mod tidy
changes
3a74bd9
to
5d397b3
Compare
Tested different functionalities of odh & kbfn-controller and everything works as expected. /lgtm |
…53232) Related to this PR: * opendatahub-io/kubeflow#349 Update go to version 1.21 to fix the failing tests and ensure consistency across all environments. CAUTION: The order of keys in releases.latest.candidate actually matters! Inspired by this Dashboard PR * #53354 (review)
/retest |
/cherrypick stable |
@jiridanek: once the present PR merges, I will cherry-pick it on top of stable in a new PR and assign it to you. 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 kubernetes-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: 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 |
7913131
into
opendatahub-io:v1.7-branch
@jiridanek: new pull request created: #359 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 kubernetes-sigs/prow repository. |
…penshift#53232) Related to this PR: * opendatahub-io/kubeflow#349 Update go to version 1.21 to fix the failing tests and ensure consistency across all environments. CAUTION: The order of keys in releases.latest.candidate actually matters! Inspired by this Dashboard PR * openshift#53354 (review)
…penshift#53232) Related to this PR: * opendatahub-io/kubeflow#349 Update go to version 1.21 to fix the failing tests and ensure consistency across all environments. CAUTION: The order of keys in releases.latest.candidate actually matters! Inspired by this Dashboard PR * openshift#53354 (review)
…penshift#53232) Related to this PR: * opendatahub-io/kubeflow#349 Update go to version 1.21 to fix the failing tests and ensure consistency across all environments. CAUTION: The order of keys in releases.latest.candidate actually matters! Inspired by this Dashboard PR * openshift#53354 (review)
https://issues.redhat.com/browse/RHOAIENG-8658, https://issues.redhat.com/browse/RHOAIENG-8651
Description
How Has This Been Tested?
Scale rhoai operator to 0, deploy both images by editing controller deployments, create notebook, stop notebook. Remove internal registry, create notebook, stop notebook.
Use images from ghcr.io/jiridanek/kubeflow:odh-notebook-controller_go21 and ghcr.io/jiridanek/kubeflow:notebook-controller_go21
Merge criteria: