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

Copy in k8s binaries to preloaded tarball so we can skip transfer #6868

Closed
priyawadhwa opened this issue Mar 3, 2020 · 1 comment · Fixed by #6870
Closed

Copy in k8s binaries to preloaded tarball so we can skip transfer #6868

priyawadhwa opened this issue Mar 3, 2020 · 1 comment · Fixed by #6870
Assignees
Labels
area/performance Performance related issues co/docker-driver Issues related to kubernetes in container kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@priyawadhwa
Copy link

No description provided.

@priyawadhwa priyawadhwa added kind/feature Categorizes issue or PR as related to a new feature. area/performance Performance related issues co/docker-driver Issues related to kubernetes in container labels Mar 3, 2020
@priyawadhwa priyawadhwa self-assigned this Mar 3, 2020
@tstromberg tstromberg added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Mar 4, 2020
@tstromberg tstromberg added this to the v1.8.0 March 5 milestone Mar 4, 2020
@afbjorklund
Copy link
Collaborator

Wouldn't it be more logical to keep these as two different tarballs ?

So you could share kubeadm between different runtimes, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/performance Performance related issues co/docker-driver Issues related to kubernetes in container kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants