-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Fix hyperkube's layer caching, and remove --make-symlinks at build time #25693
Conversation
I see this also contains #25684. If this one gets in first I'll close it. |
Oops, didn't mean to include #25684, but it was required when I tested it, and then I forgot to remove it before the commit. I may remove it so we don't get any merge conflicts. The layer patch is saving us ~130 MB/image when pulling, which is a lot |
…inks at build time
@k8s-oncall Mind merging manually? |
@k8s-bot test this please github issue: #IGNORE (tests didn't started) |
GCE e2e build/test passed for commit e7eff87. |
Automatic merge from submit-queue |
@luxas do you have more information on why or how I've just tried to reproduce any issues with the symlinks using a cut of v1.3.0 that I made today and have not seen any issues. I'd like to fix this I just don't know how to reproduce the issues right now. |
i think you mean @luxas 💃 |
Automatic merge from submit-queue cluster/images/hyperkube: re-add hyperkube busybox style symlinks Originally symlinks were added with a `--make-symlinks` command discussed in #24510 and implemented in #24511. It was backed out in #25693 because go binaries don't run in qemu and this breaks cross-building the Dockerfile for arm. In this case, due to running `hyperkube --make-symlinks`. Lets just add the symlinks manually until the upstream bug is fixed (qemu). fixes #28702 @mikedanese @thockin @yifan-gu @euank
@david-mcmahon This is required before you release. Explanation in the code.