-
Notifications
You must be signed in to change notification settings - Fork 43k
Create a single kubernetes binary for all cmds #108
Copy link
Copy link
Closed
Labels
area/build-releasearea/usabilitypriority/awaiting-more-evidenceLowest priority. Possibly useful, but not yet enough support to actually get it done.Lowest priority. Possibly useful, but not yet enough support to actually get it done.sig/cluster-lifecycleCategorizes an issue or PR as relevant to SIG Cluster Lifecycle.Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Metadata
Metadata
Assignees
Labels
area/build-releasearea/usabilitypriority/awaiting-more-evidenceLowest priority. Possibly useful, but not yet enough support to actually get it done.Lowest priority. Possibly useful, but not yet enough support to actually get it done.sig/cluster-lifecycleCategorizes an issue or PR as relevant to SIG Cluster Lifecycle.Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
As we start building a bunch of binaries the size of our output goes up. Because of go static linking, we end up with 8-10MB for each binary. Currently we 7 of these for a total of 58M (
find output/go -type f -perm +111 | xargs du -ch).If we created a single binary with a switch for which functionality users want we would have a single binary that would adapt as necessary and probably be ~10M.
I'd image we'd call this thing
kubeand by default it'd be the client binary. If you want to run a server component you would do something likekube --daemon=api-server.Thoughts?