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

question - memory footprint #303

Closed
pierreozoux opened this issue Feb 4, 2019 · 3 comments
Closed

question - memory footprint #303

pierreozoux opened this issue Feb 4, 2019 · 3 comments
Labels

Comments

@pierreozoux
Copy link

Hello!

I have an idea, and I have some questions, maybe you can help me.
There is a project called YunoHost and it is aimed at helping home users self host services like WordPress or Nextcloud on an arm computer at home.
It is nice, but based on bash let's say, and as I love k8s api, I'm wondering about k8s mem footprint on such small devices.

In a context of a one node cluster, what is the mem footprint of:

 - etcd ~ [22Mb I guess](https://coreos.com/etcd/docs/latest/benchmarks/etcd-storage-memory-benchmark.html)
- kube-api
- controller
- scheduler
- kubelet

I think our main constraint here is mem and not cpu.

Another question, do we need also a network plugin? Or as there is only one node, it is enough?

And then, what about optimization, I think there are many rooms for improvements in this context:

- remove lot of unecessary code at compilation (like aws integration and so on)
- remove the scheduler, or replace it with a dummy one
- tune the controller for home user usage instead of thousands nodes, millions pods
- tune etcd
- reimplement some functions like cronjobs?
- socket activation for all the services

I'm just thinking out loud here, if you have any ideas, please share them here, and do not hesitate to close the issue once you answered!

Thanks again and have a nice day :)

Relates to alexellis/k8s-on-raspbian#10

@pierreozoux
Copy link
Author

This is also relevant to the discussion:

solo-io/unik#182

@ktsakalozos
Copy link
Member

Hi @pierreozoux

Thank you for sharing your thoughts. You bring up a very interesting topic.

Having MicroK8s extending into IoT is in our interest. MicroK8s being a snap, arm support and the move to containerd work towards this direction. Any PRs that would improve the memory footprint without compromising functionality will be gladly accepted. Would you be willing to offer any cycles?

Thank you.

@stale
Copy link

stale bot commented Apr 4, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the inactive label Apr 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants