-
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
Drop 32bit arm from package builds #2960
Conversation
I guess having to drop existing releases from ( |
/lgtm thanks @saschagrunert |
Changelog nit: -Stopped building packages for 32bit arm platforms.
+Stopped building packages for 32 bit ARM platforms. |
Thanks! Fixed as suggested. |
that requirement seems new, right? otherwise, how did we introduce darwin/arm64 builds in 1.21 in kubernetes/kubernetes#97743 without breaking releases on still-supported <1.20 versions? |
the architectures we release for seem like they should be able to be overridden per minor version |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saschagrunert 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 |
Signed-off-by: Sascha Grunert <[email protected]>
I modified the PR to drop the |
@kubernetes/release-engineering PTAL |
@saschagrunert Should we keep this on hold until patch releases are not out? |
@xmudrii yep makes sense. |
/lgtm |
patches are out |
/retest |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
We stopped building 32bit arm releases in kubernetes/kubernetes#115742, means we cannot publish packages for that platform any more.
Which issue(s) this PR fixes:
Refers to: kubernetes/sig-release#2189
And:
linux/arm
build/release artifacts in kubernetes (32-bit arm for Raspberry PIs) kubernetes#115738Special notes for your reviewer:
We do not distinguish package builds for release branches and minor releases right now. Means this change will affect both of them.
Does this PR introduce a user-facing change?