-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Migrate to go v1.17 #7520
Comments
@rikatz: 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. |
I think we also need to upgrade github ci workflow to 1.17. |
/help |
@tao12345666333: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed 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. |
/good-first-issue |
@tao12345666333: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed 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. |
Should we make this for only v1 or both v0.x and v1? |
oh, I just that he image runner is explicit in K8s version
|
@yuswift promoted the images. Now your PR should be (all in one):
Let me know when we can merge this :) |
Thanks for your suggestion. I've committed them in #7521 |
@yuswift please cherry pick your PR to legacy branch! Thanks! |
/close |
Due to some vulnerabilities in go v1.16 we should migrate code to go v1.17
It is probably easy, but by the same time annoying to do:
The text was updated successfully, but these errors were encountered: