[QUESTION/HELP] How to specify how much system resources to allocate?

[timothystegall]

How to specify how much system resources to allocate? (CPU, RAM, etc)

Hi, I am looking for a way to specify how much system resources (CPU, RAM, maybe Storage, etc) to allocate to a cluster like how Minikube lets you: minikube config set <thing> <amount> is there a way to specify somewhat like this via the command line in k3d? I didn't see anything related to it in the documentation at k3d.io. Thank you! 😃

Scope of your Question

k3d version v4.4.4
k3s version v1.20.6-k3s1 (default)

[iwilltry42]

Hi @tim-steg , thanks for opening this discussion!
Unlike Minikube (if default is still VM), k3d does not run a virtual machine that you can limit in resources.
Since the k3s containers are spawned in privileged mode, we also cannot leverage docker functionality to restrict their memory usage.
However, if you want to emulate restrictions to your pods, we have the --servers-memory and --agents-memory flags now which create fake meminfo files to tell cadvisor (in k3s in docker) wrong memory details.
If you want to ensure that your system doesn't get overloaded, then k3d doesn't give you any tools for that (but you can limit the Docker for Desktop VM, if you're on MacOS/Windows), if you really need this.
Apart from that, k3d (thanks to k3s) is pretty lightweight in itself.

[timothystegall]

Okay awesome, thank you! Also, is there a way to enable ssh connectivity on the main server-0 container out of the box? I have a special use-case for it. Thanks again!

[iwilltry42]

You're welcome :)
Do you need "real SSH"? Because you can just use docker exec -it k3d-<clustername>-server-0 sh to get an interactive shell inside the node container.
There's no SSHD running inside the k3s containers (and they're not based off of an OS image).

[lukepolo]

We are trying to use SSH to rsync, we have something similar to tilt (may switch to that anyways)

[iwilltry42]

Sorry for the late reply @lukepolo !
I fear that that won't work then out of the box. You could obviously do some tricks with spawning ssh server pods on the k3d cluster that mount the host root and then use port-mapping to get access to the ssh port.. but nothing built into the k3s image (it's basically busybox + k3s in an almost empty filesystem).

[lukepolo]

awesome, thanks for the reply, will try that!