Hi Folks, I think I have run into an issue: I have a very early setup of my k3s setup via https://github.com/k3s-io/k3s-ansible with 3 Control Nodes (2 vCores, 4 GB RAM) and 2 Worker Nodes (1 vCore, 512 MB RAM) like described here https://docs.k3s.io/installation/requirements#hardware I have setuped longhorn with traefik (for the dashboard) following mostly the official documentation (https://longhorn.io/docs/1.8.1/deploy/install/install-with-kubectl/ and https://longhorn.io/docs/1.8.1/deploy/accessing-the-ui/longhorn-ingress/) I only changed the nginx parts to traefik. Via the Dashboard I have disabled sheduling for the CN and on my WN I added a second block device for scheduling and disabled the boot drive. Now when I try to deploy https://longhorn.io/docs/1.8.1/nodes-and-volumes/volumes/create-volumes/ I see huge CPU spikes on the WN and they are shown occasinally as DOWN on the Dashboard.

I do not use K3s, but 1 core and 512MB is "minimum requirements" as the doc says

Is there any resource how to scale for Longhorn?

that is a valid question and so far I am not seeing an answer in docs

You definitely do not have enough resources for LH

@creamy-pencil-82913 good to know, thought "Longhorn is a lightweight, reliable and easy-to-use distributed block storage system for Kubernetes." would go well with the minimum of k3s, since no further informations provided. Already bumped my nodes to 4 Cores, not sure if RAM is the issue.

Lightweight may mean something different to you, than it does to the hyperconverged storage market. You should probably give LH 1 core and 512m in addition to whatever you need for base OS, Kubernetes, and then your workload on top of all that.