https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
r
Here are some outputs once I have started everything then torn it all down.
Copy code
k3d-rocketyard in shipyard on  main [$] via  v20.12.2 
❯ kubectl top node --sort-by memory
NAME                      CPU(cores)   CPU%   MEMORY(bytes)   MEMORY%   
k3d-rocketyard-server-0   102m         1%     3273Mi          18%       

k3d-rocketyard in shipyard on  main [$] via  v20.12.2 
❯ kubectl top pods -A --sort-by memory
NAMESPACE     NAME                                      CPU(cores)   MEMORY(bytes)   
kube-system   metrics-server-54fd9b65b-5mwv5            7m           26Mi            
kube-system   coredns-6799fbcd5-p99fr                   4m           22Mi            
kube-system   local-path-provisioner-6c86858495-4fhds   1m           11Mi
Copy code
PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
   87     7 root     S    6881m  37%   1% /bin/k3s server
  192    87 root     S    5610m  30%   0% containerd
c
you could try profiling the k3s process to see where the memory allocations are?
k3s has an --enable-pprof flag, when that is enabled you can connect go memory and cpu profiling tools
2 Views
Open in Slack
PreviousNext
Powered by