[PLEASE READ] Kubernetes 1.19 will be built using go1.15
141 views
Skip to first unread message
Stephen Augustus
Jul 27, 2020, 4:03:57 PM7/27/20
to Kubernetes developer/contributor discussion, kubernetes-sig-release, release-...@kubernetes.io, Kubernetes Release Team, kubernetes-sig-testing
Kubernetes Community,
As you may have heard during SIG Release (Release Engineering, Release Team) meetings in the last few weeks, we're working on preparing Kubernetes 1.19 to be built using go1.15.
This weekend, we landed a significant step: targeting kubernetes/kubernetes@master to go1.15rc1[1]
This morning, that work was fast-forwarded into the release-1.19 branch[2][3].
Less than an hour ago, kubekins-e2e and krte (KinD Runtime Environment) images were bumped[4][5] to use go1.15rc1.
If you are running Prowjobs using any of the following images, your code is now being tested against go1.15rc1:
If you are a reviewer/approver/maintainer of jobs using these images, please consider starting to use go1.15rc1 locally.
https://golang.org/dl/#unstable --> go get golang.org/dl/go1.15rc1
A few asks...
Release Team--
Please continue to keep an eye on CI Signal and issues. For issues that look like Go toolchain issues, immediately tag @kubernetes/release-engineering.
Release Managers--
Assist with CI Signal queries around Golang (as you're able) and be extra diligent about responding to team mentions (@kubernetes/release-engineering, @kubernetes/release-managers).
Contributors--
Err on the side of paranoia.
If you see a Golang issue/test failure that you don't usually encounter in your usual workflow, file a detailed issue, tag @kubernetes/release-engineering, and apply the 1.19 milestone (if you have permissions to do so).
As far as I know, this is the first time we've started consuming a Golang version on a wider scale, ahead of the official minor release.
We ask that you expect some hiccups, be patient as we work through them, and help where you can to ensure a successful, on-time delivery of Kubernetes 1.19.
Special thanks to a few folks:
@liggitt - For helping out the past few days (and specifically over this weekend) to carry the go1.15rc1 PR[1] over the finish line
@dims, @BenTheElder - For their testing prowess
@fejta, @jayconrod - For building my knowledge in bazel and providing reviews to enable us to test Go pre-releases
@FiloSottile - For providing some dependency reviews on the go1.15rc1
I'll continue to send updates to this thread as we hit new milestones and will be tracking overall progress in this issue: https://github.com/kubernetes/release/issues/1421
-- Stephen
[1]: https://github.com/kubernetes/kubernetes/pull/93264
[2]: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1595839974416300
[3]: https://github.com/kubernetes/kubernetes/compare/d3f7c6e8426...d01fde69678
[4]: https://github.com/kubernetes/test-infra/pull/18475
[5]: https://github.com/kubernetes/test-infra/pull/18468
As you may have heard during SIG Release (Release Engineering, Release Team) meetings in the last few weeks, we're working on preparing Kubernetes 1.19 to be built using go1.15.
This weekend, we landed a significant step: targeting kubernetes/kubernetes@master to go1.15rc1[1]
This morning, that work was fast-forwarded into the release-1.19 branch[2][3].
Less than an hour ago, kubekins-e2e and krte (KinD Runtime Environment) images were bumped[4][5] to use go1.15rc1.
If you are running Prowjobs using any of the following images, your code is now being tested against go1.15rc1:
- kubekins-e2e-master (gcr.io/k8s-testimages/kubekins-e2e:v20200726-f8d6253-master)
- kubekins-e2e-1.19 (gcr.io/k8s-testimages/kubekins-e2e:v20200726-f8d6253-1.19)
- kubekins-e2e-experimental (gcr.io/k8s-testimages/kubekins-e2e:v20200726-f8d6253-experimental)
- krte-master (gcr.io/k8s-testimages/krte:v20200726-f8d6253-master)
- krte-1.19 (gcr.io/k8s-testimages/krte:v20200726-f8d6253-1.19)
- krte-experimental (gcr.io/k8s-testimages/krte:v20200726-f8d6253-experimental)
If you are a reviewer/approver/maintainer of jobs using these images, please consider starting to use go1.15rc1 locally.
https://golang.org/dl/#unstable --> go get golang.org/dl/go1.15rc1
A few asks...
Release Team--
Please continue to keep an eye on CI Signal and issues. For issues that look like Go toolchain issues, immediately tag @kubernetes/release-engineering.
Release Managers--
Assist with CI Signal queries around Golang (as you're able) and be extra diligent about responding to team mentions (@kubernetes/release-engineering, @kubernetes/release-managers).
Contributors--
Err on the side of paranoia.
If you see a Golang issue/test failure that you don't usually encounter in your usual workflow, file a detailed issue, tag @kubernetes/release-engineering, and apply the 1.19 milestone (if you have permissions to do so).
As far as I know, this is the first time we've started consuming a Golang version on a wider scale, ahead of the official minor release.
We ask that you expect some hiccups, be patient as we work through them, and help where you can to ensure a successful, on-time delivery of Kubernetes 1.19.
Special thanks to a few folks:
@liggitt - For helping out the past few days (and specifically over this weekend) to carry the go1.15rc1 PR[1] over the finish line
@dims, @BenTheElder - For their testing prowess
@fejta, @jayconrod - For building my knowledge in bazel and providing reviews to enable us to test Go pre-releases
@FiloSottile - For providing some dependency reviews on the go1.15rc1
I'll continue to send updates to this thread as we hit new milestones and will be tracking overall progress in this issue: https://github.com/kubernetes/release/issues/1421
-- Stephen
[1]: https://github.com/kubernetes/kubernetes/pull/93264
[2]: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1595839974416300
[3]: https://github.com/kubernetes/kubernetes/compare/d3f7c6e8426...d01fde69678
[4]: https://github.com/kubernetes/test-infra/pull/18475
[5]: https://github.com/kubernetes/test-infra/pull/18468
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages