-
Notifications
You must be signed in to change notification settings - Fork 502
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
[go1.17] Build images for go1.17 #2211
Conversation
/retest |
/lgtm 🤞🏾 |
@@ -1,11 +1,11 @@ | |||
variants: | |||
go1.17-buster: | |||
CONFIG: 'go1.17-buster' | |||
IMAGE_VERSION: 'v2.3.1-go1.17rc2-buster.0' | |||
IMAGE_VERSION: 'v2.3.1-go1.17-buster.0' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can look at doing a bullseye
variant once it's available for distroless: GoogleContainerTools/distroless#780
I think we're waiting for this PR before the new upstream builds trigger: docker-library/official-images#10739 |
Yep! From docker-library/official-images#10739 (comment):
|
/retest |
1 similar comment
/retest |
Potential flake: |
Potential flake: |
One more time before I start debugging with purpose... |
Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
- kube-cross:v1.23.0-go1.17-buster.0 - go-runner:v2.3.1-go1.17-buster.0 Signed-off-by: Stephen Augustus <[email protected]>
Tests appear to be passing, but contexts are stuck due to the GCB build queue getting from previous runs: |
/test all |
On second thought, I'm going to hold the proposed changes in #2210 for another PR since:
Ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, justaugustus 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 |
/test pull-release-image-go-runner |
1 similar comment
/test pull-release-image-go-runner |
Timeout: |
What type of PR is this?
/kind feature
/area dependency
What this PR does / why we need it:
kube-cross: Drop non-legacy go1.15 variant
kube-cross: Remove etcd from non-legacy builds (ref: kube-cross: Build v1.16.5-canary-2 image without etcd #2124, kube-cross: Build v1.22-dev-1 image using etcd v3.5.0 #2123 (comment))
images: Enforce Debian codenames for Golang-based images
When there are multiple image builds in flight both upstream and downstream,
we can run into situations where a new Debian version becomes the default for
image builds, which can have unintended side-effects across release branches.
Here we use explicit pairings of Golang/Debian versions to retrieve images
Example:
FROM golang:1.16.7-buster
kube-cross: Use OS codenames to construct clearer versions for images
Uses the following nomenclature:
v<kubernetes-major>-go<go-major>-<os-codename>.<revision>
Example:
v1.23.0-go1.17-buster.0
[go1.17] Build images for go1.17
ref:
/assign @saschagrunert @puerco @cpanato
cc: @kubernetes/release-engineering @dims @dekkagaijin @dlorenc
Which issue(s) this PR fixes:
Special notes for your reviewer:
Image build presubmits may fail as upstream s390x jobs appear as "unstable" at the time of this PR's creation. (cc: @mkumatag @tianon)
Does this PR introduce a user-facing change?