This message was deleted.
# k3sa
adamant-kite-43734
11/21/2024, 11:05 AMThis message was deleted.
h
hundreds-evening-84071
11/21/2024, 12:29 PMyou can start with looking at resource utilization of pods across all namespaces:
kubectl top po -Ajournalctl -u k3s-server.servicejournalctl -u k3s.servicehundreds-evening-84071
11/21/2024, 12:30 PMlook at the release notes to see if this is a known issue for the version you have running?
b
billowy-computer-46613
11/21/2024, 12:52 PMregarding
kubectl top pobillowy-computer-46613
11/21/2024, 12:52 PMIts not the pods who consume the cpu, but the k3s server process itself
billowy-computer-46613
11/21/2024, 3:30 PMThe main "k3s server" process has a lot of threads. I know that some them are:
• api-server
• scheduler
• kind (sqlite wrapped as etc)
but I have 113 threads. How can I figure out what each thread does?
h
hundreds-evening-84071
11/21/2024, 3:36 PMI no long run k3s so from k3s perspective I don't know...
from Linux side you can check what each process is doing with lsof
n
nutritious-tomato-14686
11/25/2024, 7:34 PMComing to this late, but you can watch all the pids associated with the K3s cgroup with
systemd-cgtop system.slice/k3s.service5 Views