-
Notifications
You must be signed in to change notification settings - Fork 604
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
Flux components Go v1.17 upgrade #2016
Comments
We may want to delay this as Go 1.17 mod doesn't work with x/crypto packages. |
Got it, thanks for the information. We can use this when the time comes. |
I see that some issues were fixed, e.g. golang/go#46761 I propose we test the upgrade in source-controller and make sure the multi-arch build works. |
Let's block this until Kubernetes client-go and controller-runtime switch to Go 1.17 https://github.com/kubernetes-sigs/controller-runtime/blob/master/go.mod |
Sounds good to me. |
So Kubernetes has switched to Go 1.17 for compiling but go.mod is still on 1.16 format. I propose we do the same, bump Go in CI and in the Dockerfiles to 1.17, leave go.mod as it. |
@stefanprodan I'm not sure if that applies to our repos. I tried to search for a reason why they decided to do that and found two relevant comments here and here. It looks like this is just because the reporting tools they use are not (yet?) supporting the dependency graph information that go mod 1.17 handles. On a side note, controller-runtime has the mod changes in place in master right now but there's not yet a released version containing the change if we're still waiting for that to happen. |
controller-runtime with Go .1.7 has been released https://github.com/kubernetes-sigs/controller-runtime/blob/v0.11.0/go.mod#L3 @relu Can you update controller-runtime in fluxcd/pkg and rebase your PR? I'm for getting this in now. |
@stefanprodan definitely, I'll get to it. |
This is an umbrella issue to keep track of the Go version upgrade work across all of the Flux components.
The text was updated successfully, but these errors were encountered: