Resource Profiling

This section captures the results of tests to determine minimum resource requirements for K3s.

The results are summarized as follows:

• Scope of Resource Testing
• Components Included for Baseline Measurements
• Methodology
• Environment
• Baseline Resource Requirements
  • K3s Server with a Workload
  • K3s Cluster with a Single Agent
  • K3s Agent
• Analysis
  • Primary Resource Utilization Drivers
  • Preventing Agents and Workloads from Interfering with the Cluster Datastore

Scope of Resource Testing

The resource tests were intended to address the following problem statements:

• On a single-node cluster, determine the legitimate minimum amount of CPU, memory, and IOPs that should be set aside to run the entire K3s stack server stack, assuming that a real workload will be deployed on the cluster.
• On an agent (worker) node, determine the legitimate minimum amount of CPU, memory, and IOPs that should be set aside for the Kubernetes and K3s control plane components (the kubelet and k3s agent).

Components Included for Baseline Measurements

The tested components are:

• K3s v1.26.5 with all packaged components enabled
• Prometheus + Grafana monitoring stack
• Kubernetes Example Nginx Deployment

These are baseline figures for a stable system using only K3s packaged components (Traefik Ingress, Klipper lb, local-path storage) running a standard monitoring stack (Prometheus and Grafana) and the Guestbook example app.

Resource figures including IOPS are for the Kubernetes datastore and control plane only, and do not include overhead for system-level management agents or logging, container image management, or any workload-specific requirements.

Methodology

A standalone instance of Prometheus v2.43.0 was used to collect host CPU, memory, and disk IO statistics using prometheus-node-exporter installed via apt.

systemd-cgtop was used to spot-check systemd cgroup-level CPU and memory utilization. system.slice/k3s.service tracks resource utilization for both K3s and containerd, while individual pods are under the kubepods hierarchy.

Additional detailed K3s memory utilization data was collected from kubectl top node using the integrated metrics-server for the server and agent processes.

Utilization figures were based on 95th percentile readings from steady state operation on nodes running the described workloads.

Environment

Baseline Resource Requirements

This section captures the results of tests to determine minimum resource requirements for basic K3s operation.

K3s Server with a Workload

These are the requirements for a single-node cluster in which the K3s server shares resources with a simple workload.

The CPU requirements are:

The Memory Requirements are:

The Disk requirements are:

K3s Cluster with a Single Agent

These are the baseline requirements for a K3s cluster with a K3s server node and a K3s agent, but no workload.

K3s Server

The CPU requirements are:

The Memory Requirements are:

K3s Agent

The requirements are:

Analysis

This section captures what has the biggest impact on K3s server and agent utilization, and how the cluster datastore can be protected from interference from agents and workloads.

Primary Resource Utilization Drivers

K3s server utilization figures are primarily driven by support of the Kubernetes datastore (kine or etcd), API Server, Controller-Manager, and Scheduler control loops, as well as any management tasks necessary to effect changes to the state of the system. Operations that place additional load on the Kubernetes control plane, such as creating/modifying/deleting resources, will cause temporary spikes in utilization. Using operators or apps that make extensive use of the Kubernetes datastore (such as Rancher or other Operator-type applications) will increase the server’s resource requirements. Scaling up the cluster by adding additional nodes or creating many cluster resources will increase the server’s resource requirements.

K3s agent utilization figures are primarily driven by support of container lifecycle management control loops. Operations that involve managing images, provisioning storage, or creating/destroying containers will cause temporary spikes in utilization. Image pulls in particular are typically highly CPU and IO bound, as they involve decompressing image content to disk. If possible, workload storage (pod ephemeral storage and volumes) should be isolated from the agent components (/var/lib/rancher/k3s/agent) to ensure that there are no resource conflicts.

Preventing Agents and Workloads from Interfering with the Cluster Datastore

When running in an environment where the server is also hosting workload pods, care should be taken to ensure that agent and workload IOPS do not interfere with the datastore.

This can be best accomplished by placing the server components (/var/lib/rancher/k3s/server) on a different storage medium than the agent components (/var/lib/rancher/k3s/agent), which include the containerd image store.

Workload storage (pod ephemeral storage and volumes) should also be isolated from the datastore.

Failure to meet datastore throughput and latency requirements may result in delayed response from the control plane and/or failure of the control plane to maintain system state.