-
Notifications
You must be signed in to change notification settings - Fork 505
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
images: Build go-runner:buster-v2.2.1 #1752
Conversation
No image content changes. Rebuild to pick up fixes to the distroless images to include an `armhf` variant in their manifests to allow us to continue releasing all of the arch artifacts we do today. Signed-off-by: Stephen Augustus <[email protected]>
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
/lgtm |
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: hasheddan, justaugustus, Verolop, xmudrii 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 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Part of go1.15.5 updates: #1651.
images: Build go-runner:buster-v2.2.1
No image content changes.
Rebuild to pick up fixes to the distroless images to include an
armhf
variant in their manifests to allow us to continue releasing all of the
arch artifacts we do today.
ref: Add armhf support for the forthcoming K8s release GoogleContainerTools/distroless#638
Thanks to @mattmoor and @chanseokoh for pushing this along on the
distroless
side! 💕Signed-off-by: Stephen Augustus [email protected]
/assign @hasheddan @puerco
cc: @kubernetes/release-engineering
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?