Kubelite takes 1.5GB for a 16GB machine
See original GitHub issueSummary
I have a 16GB machine which installed microk8s. However, kubelite
itself takes 1.5GB, which seems a lot considering the total memory is so limited.
Is it a bug with microk8s, or is microk8s just this memory-hungry? Thanks.
What Should Happen Instead?
less memory
Reproduction Steps
- n/s
Introspection Report
[cannot post here for privacy, can you give an email so I will send it]
Can you suggest a fix?
willing to pr
Are you interested in contributing with a fix?
yes
Issue Analytics
- State:
- Created a year ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @fzyzcjy,
What version of Kubernetes are you using? What workloads are you running?
Kubelite runs all the Kubernetes services started from a single process. This includes the control plane unless you
microk8s join
the nodes with the--worker
flag. In past MicroK8s versions Kubelite also packs the datastore used by K8s.Here are some configuration options to reduce k8s memory footprint:
microk8s disable ha-cluster
immediately after you snap installed MicroK8s.--worker
flag--runtime-config
argument [1] to not load the APIs you do not use. THis argument should be added in/var/snap/microk8s/current/args/kube-apiserver
.[1] https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/
Thank you!
(Btw I was on 1.21 because 1.22 has a lot of API changes…)