-
Notifications
You must be signed in to change notification settings - Fork 4k
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 Cluster Autoscaler to go 1.17 #4587
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MaciekPytel 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 |
/lgtm nit: It might be worth pointing out the difference in comments somewhere (e.g. add a comment to the Dockerfile saying that this should be the authoritative version and why it's different than go.mod + an opposite comment in go.mod). I know I've been using the version from go.mod as the authoritative one so far, others might be surprised as well. |
/hold cancel |
/lgtm |
Kubernetes 1.23 uses that version and the vendored code no longer compiles using go1.16 (which we used previously). Following the upstream Kubernetes I'm leaving the go version in go.mod file at 1.16, as bumping it to 1.17 changes go mod behavior in a way that breaks some kubernetes tooling (kubernetes/kubernetes#105563 (comment) for context).
CA no longer compiles on go1.16.
As of go1.17 both tags are expected to exist simultaneously. Added tags in all cluster autoscaler files. Added verify-gomod.sh exceptions for non-compliant autogenerated VPA files.
/lgtm |
This is a partial cherry-pick of a #4567.
Kubernetes has moved to go 1.17 and no longer compiles on go 1.16 (currently used by CA). This bumps CA to go1.17 and is a prerequisite to updating deps (which I'll do in a follow-up PR).
Some gotchas: