-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Update ingress to go 1.17 #7521
Conversation
@yuswift: This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The 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/test-infra repository. |
Hi @yuswift. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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/test-infra repository. |
/cc @rikatz |
/ok-to-test |
I think we need to retest. |
Yeah, that K8s v1.17 I think is benign but on a different note, maybe lets wait for more reviews. At least we now know that a simple pass does not break anything major. |
/retitle Migrate to go 1.17 |
@yuswift: Re-titling can only be requested by trusted users, like repository collaborators. 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/test-infra repository. |
@rikatz |
/retitle Update ingress to go 1.17 |
About kube-webhook-gen it's not as urgent as ingress (it does not receives connections, etc) but in a future yeah, we should probably update it |
About the error: please run go mod tidy locally with go v1.17 and make a new commit :) |
Done :) |
@yuswift thanks. A last change, so boilerplate verification can pass, in: https://github.com/kubernetes/ingress-nginx/blob/main/hack/boilerplate/boilerplate.py#L196 Change to: r"^((// \+build.*\n)|(//go:build.*\n))+\n", re.MULTILINE) |
nice catch! done :) |
/lgtm Thanks. We should probably cherry pick this to "legacy" branch so new legacy releases will use Go 1.17 as well |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rikatz, yuswift 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 |
/cherry-pick legacy |
* fix boilerplate verification * fix go fmt error * fix go mod error * bump e2e-test-runner version * bump github ci workflow to go 1.17 * bump go.mod to 1.17
* bump go.mod to 1.17 * bump github ci workflow to go 1.17 * bump e2e-test-runner version * fix go mod error * fix go fmt error * fix boilerplate verification
What this PR does / why we need it:
Types of changes
Which issue/s this PR fixes
part of #7520
How Has This Been Tested?
Checklist: