-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Reduce memory footprint of build #391
Comments
What is the OS?
|
I'm using go version go1.7.5 linux/amd64 on FC25. The build only quickly peaks at using > 2G mem when linking cilium-agent. Running |
Based on some research, one of the main reasons is the linking to the kubernetes go-client which pulls in a huge dependency chain. |
This is no longer a big issue, closing. |
Following merge of cilium#400, we broke cilium#391. This PR fixes the issue by refactoring both EKS workflows to be consistent with other workflows, now that we are creating a cluster with nodes available right away just like on other platforms, and thus do not need to split the `install`/`test` steps anymore. Fixes 3d2fbdbecb22b37b32417b6a548be1ae212ba3e5 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
The build currently requires between 3-4GB of memory which is completely insane.
The text was updated successfully, but these errors were encountered: