3 ms·
I recently tried Mikrok8s from Canonical and at idle (as in not running any of my containers) it ranges from 5% to 15%. I hope this product doesn't suffer the s
by lloydatkinson 3y ago
I recently tried Mikrok8s from Canonical and at idle (as in not running any of my containers) it ranges from 5% to 15%. I hope this product doesn't suffer the same wastage.
- AugustoCAS 3y agoI had the same problem (there's a github issue about this: https://github.com/canonical/microk8s/issues/2186 https://github.com/canonical/microk8s/issues/2186). I swapped to k3s and the usage was half of what microk8s used.
- millerhooks 3y agoThere are issues with the grvfs client that gets into a race condition with the disc volumes. It will saturate the max_connections and eat resources at idle. Not sure if this is your issue, I have yet to find a real solution other than uninstalling grvfs-backends and bumping the max user and connections. I got this workaround added to the charmed kubeflow QuickStart. It’s not the correct solution though and I’m pretty spent on the issue.