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
Official ARM builds for every new release #19769
Official ARM builds for every new release #19769
Conversation
|
Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist") If this message is too spammy, please complain to ixdy. |
1 similar comment
|
Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist") If this message is too spammy, please complain to ixdy. |
|
Labelling this PR as size/M |
|
@k8s-bot ok to test |
| @@ -1,4 +1,4 @@ | |||
| # Copyright 2014 Google Inc. All rights reserved. | |||
| # Copyright 2016 Google Inc. All rights reserved. | |||
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.
Please don't bump the copyright on the file unless it's been basically rewritten (it hasn't).
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.
Aha, thought it could be updated... No problem
|
GCE e2e build/test failed for commit e7f388d904953b155665fc19c5228ac385028a6d. |
|
@zmerlynn Do you have any specific reason why you are building test targets for all client platforms? Isn't that a little bit unnecessary and slower? Of course test targets should be made for I know that it might be another discussion though and that it might break backwards-compability (I don't know if you run integration tests on windows) |
|
FYI also @ihmccreery @david-mcmahon |
|
@luxas: Yes, we could probably take the test code out of the client build. |
| darwin/amd64 | ||
| darwin/386 | ||
| windows/amd64 | ||
| windows/386 |
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.
Did you add 32-bit windows for a reason?
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.
Because I saw that a compiler in the earlier kube-build:cross was built for windows/386, but it wasn't listed as a client platform. Supposed it just had been forgotten.
But it doesn't harm to build kubectl for 32-bit win also.
|
This looks okay. I'm a little concerned about bumping |
|
Yes, I have no idea where I pulled the other number from. |
e7f388d
to
2360e14
Compare
| @@ -97,6 +97,7 @@ readonly GCS_STAGE="${LOCAL_OUTPUT_ROOT}/gcs-stage" | |||
| # The set of master binaries that run in Docker (on Linux) | |||
| # Entry format is "<name-of-binary>,<base-image>". | |||
| # Binaries are placed in /usr/local/bin inside the image. | |||
| # TODO: Make base images for multiple server platforms | |||
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.
@zmerlynn Do you have some suggestions how to nicely handle this?
We need to be able to specify different base images for different arches
|
GCE e2e build/test failed for commit 2360e14e8225c02c1be9363c21a43ec5edbfc334. |
|
Looks like a e2e flake. But some test didn't start in time or something... |
|
GCE e2e build/test failed for commit d58844e952f8c6adc35cc7472c1b26b90fca398d. |
|
To rebase to I'll try to get working this only for |
d58844e
to
c969c04
Compare
|
GCE e2e test build/test passed for commit c969c04. |
|
LGTM |
|
@k8s-bot test this Tests are more than 48 hours old. Re-running tests. |
|
GCE e2e test build/test passed for commit c969c04. |
|
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
|
GCE e2e test build/test passed for commit c969c04. |
|
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
|
GCE e2e test build/test passed for commit c969c04. |
|
Automatic merge from submit-queue |
Auto commit by PR queue bot
|
@luxas To add this as a release note, add the release-note label and update the PR description to whatever you want the release note to say. |
|
@david-mcmahon adding a label requires repo write access which not everyone has |
|
@mikedanese thanks for the clarification. Adding release-note label. @luxas please adjust release note to taste. |
This PR features support for building
arm(,arm64andppc64le) binaries dynamically or statically onamd64hosts. It builds docker images forkube-apiserver,kube-controller-manager,kube-scheduler,kube-proxyfor the new architectures and pushes them.Bug fixed:
hyperkube(legacy name forhyperkube-amd64) is pushed too when releasing for compability with older setupsEarlier:
armamd64hostsarm64orppc64lesupport at all.Now:
arm(,ppc64le,arm64when we havego1.5)amd64hostskubeletandhyperkubeespecially are built dynamically to includecAdvisorarm64to build server targetsarm64: Add linux_arm64 support onsi/ginkgo#209 and Update ginkgo and bolt Godeps so k8s builds on ARM64 #20546arm,arm64,ppc64le, so test targets are only built forlinux/amd64,darwin/amd64andwindows/amd64.windows/386client support addedTracking issue: #17981
Depends on: #14873
A bit related to: #19703
When this is merged, it has the advantage that builds will fail when trying to merge only-working-on-amd64 code for the server targets, so it's easily noticed.
This is WIP for now because #14873 hasn't merged yet (and I have to rebase after that)
Thoughts? This will make Kubernetes more cross-platform, and that will be awesome👍
@brendandburns @thockin @zmerlynn @fgrzadkowski @david-mcmahon @mikedanese @gmarek @wojtek-t @qq511700505