-
Notifications
You must be signed in to change notification settings - Fork 640
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
guestagent binaries are too huge (k8s.io
deps should be replaced with exec("kubectl")
?)
#3237
Comments
Most of this comes from adding the Kubernetes port forwarding (#1355) in ❯ tar tvfz lima-0.14.2-Darwin-arm64.tar.gz| grep guest
-rw-r--r-- 0 runner staff 7139328 23 Dec 2022 ./share/lima/lima-guestagent.Linux-x86_64
-rw-r--r-- 0 runner staff 6946816 23 Dec 2022 ./share/lima/lima-guestagent.Linux-riscv64
-rw-r--r-- 0 runner staff 6881280 23 Dec 2022 ./share/lima/lima-guestagent.Linux-aarch64
❯ tar tvfz lima-0.15.0-Darwin-arm64.tar.gz| grep guest
-rw-r--r-- 0 runner staff 38367232 28 Feb 2023 ./share/lima/lima-guestagent.Linux-x86_64
-rw-r--r-- 0 runner staff 37027840 28 Feb 2023 ./share/lima/lima-guestagent.Linux-riscv64
-rw-r--r-- 0 runner staff 36765696 28 Feb 2023 ./share/lima/lima-guestagent.Linux-aarch64 Not sure what to do about this. Are you concerned about the size of the Lima distribution, or about the amount of data we add to I do expect the size to grow a little more when we add API based scrapers for dockerd and containerd as well, but nothing like the size of the k8s libraries. |
Probably we can eliminate a bunch of deps just by modifying
Both |
k8s.io
deps should be replaced with exec("kubectl")
?)
How would that work for creating a service watcher that gets notified "immediately" when the service definitions change? One of the reasons to switch to API based scrapers is to get rid of the 3 seconds delay between ports being opened/closed and the corresponding change being made to the host socket. So I could see us adding a slimmed-down guestagent for when you don't need/want the API based scrapers. That would reduce the size of Not sure if any of that is worth the effort; most people don't seem to care. |
An alternative could be to implement scrapers as independent processes. That means the hostagent would have to deal with the de-duplication when multiple scrapers report the same port changes. But I think we already have a race condition for this in the current code. |
Why can't we use |
Maybe we can; I will discuss with @Nino-K. I think he just finished merging all the scrapers from the Rancher Desktop Windows guestagent with the Lima guestagent, so he will know better than me. |
You can use |
The footprint of the guestagent binaries has grown from 6.2M + 6.6M to 46M + 45M + 46M + 48M through the four years
The text was updated successfully, but these errors were encountered: