Skip to content
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

Build hyperkube in hack/local-up-cluster instead of separate binaries #25627

Merged
merged 1 commit into from
May 15, 2016

Conversation

luxas
Copy link
Member

@luxas luxas commented May 15, 2016

This speeds up the build time a lot.
Also add arm64 as a valid arch

This is quite trivial. Let's get it in asap
@thockin @pmorie @liggitt @eparis @zmerlynn @smarterclayton

…parate binaries. Also add arm64 as a valid arch
@luxas
Copy link
Member Author

luxas commented May 15, 2016

This isn't covered by e2e

@k8s-github-robot k8s-github-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. release-note-label-needed labels May 15, 2016
@luxas luxas added release-note-none Denotes a PR that doesn't merit a release note. and removed release-note-label-needed labels May 15, 2016
@k8s-bot
Copy link

k8s-bot commented May 15, 2016

GCE e2e build/test passed for commit 8e64b5f.

@smarterclayton
Copy link
Contributor

Part of the purpose of hack/local-up-cluster is to validate that the individual components start cleanly (i.e., to test cmd/kube-apiserver/... in isolation). I wouldn't necessarily expect us to make this change until we were adding hyperkube to the core setup.

@luxas
Copy link
Member Author

luxas commented May 15, 2016

Okay, understand that.
Can I create an option for it?

@smarterclayton
Copy link
Contributor

On the other hand, the only place local up is used is to assist local development, and if hyperkube is faster then I think that's more important. E2e probably covers the other entry point sufficiently. So I think this is a net win.

@smarterclayton smarterclayton added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 15, 2016
@luxas
Copy link
Member Author

luxas commented May 15, 2016

Maybe we should add a release note for this so people notice that it has changed?

@smarterclayton smarterclayton added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-none Denotes a PR that doesn't merit a release note. labels May 15, 2016
@k8s-github-robot
Copy link

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit eae9863 into kubernetes:master May 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants