https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
a
Is your control plane node also running cluster workload or is it dedicated to only being the control plane?
p
Only for Control Plane
Only 4 Pods running on the Control Plane
a
Copy code
ps -eo pcpu,pid,user,args | sort -k 1 -r | head -10
This will tell you the top-10 processes that are using the CPU.
p
Copy code
%CPU     PID USER     COMMAND
 370   14212 root     /usr/local/bin/k3s server
 3.0     677 root     /usr/bin/litestream replicate
 1.8     414 root     /lib/systemd/systemd-journald
 1.7   20372 root     cilium-agent --config-dir=/tmp/cilium/config-map
 1.6   14291 root     containerd -c /var/lib/rancher/k3s/agent/etc/containerd/config.toml -a /run/k3s/containerd/containerd.sock --state /run/k3s/containerd --root /var/lib/rancher/k3s/agent/containerd
 0.8     682 syslog   /usr/sbin/rsyslogd -n -iNONE
 0.3     107 root     [kswapd0]
 0.2      43 root     [kcompactd0]
 0.1   21438 root     /velero node-agent server
a
So it is definitely the k3s binary that's doing it.
what version are you running?
p
1.26.3
a
looking at https://github.com/k3s-io/k3s/issues/294. It looks like it's a recurring issue.
p
Yeah but i have 100% usage all the time and not 30 - 40%. The API Server is very very slow
a
If one of the Rancher folks don't answer you here I would suggest putting in a new issue with as much detail as you can.
20 Views
Open in Slack
PreviousNext
Powered by