| CARVIEW |
Select Language
HTTP/2 200
server: GitHub.com
content-type: text/html; charset=utf-8
last-modified: Mon, 15 Dec 2025 18:05:02 GMT
access-control-allow-origin: *
strict-transport-security: max-age=31556952
etag: W/"69404dce-385c"
expires: Tue, 03 Feb 2026 00:52:54 GMT
cache-control: max-age=600
content-encoding: gzip
x-proxy-cache: MISS
x-github-request-id: 4C69:85321:18169:2015C:6981448E
accept-ranges: bytes
date: Tue, 03 Feb 2026 04:06:59 GMT
via: 1.1 varnish
age: 58
x-served-by: cache-bom-vanm7210068-BOM
x-cache: HIT
x-cache-hits: 1
x-timer: S1770091620.814416,VS0,VE1
vary: Accept-Encoding
x-fastly-request-id: dec69b1063c69b896324f5fa58a9b7b7930c483e
content-length: 4686
K3s

1. Download K3s - latest release: x86_64, ARMv7, and ARM64 are supported
Lightweight Kubernetes
The certified Kubernetes distribution built for IoT & Edge computing
This won't take long…
curl -sfL https://get.k3s.io | sh -
# Check for Ready node, takes ~30 seconds
sudo k3s kubectl get node
For detailed installation, refer to the docs
Great For
Edge
IoT
CI
ARM
Why Use K3s
Perfect for Edge
K3s is a highly available, certified Kubernetes distribution designed for production workloads in unattended, resource-constrained, remote locations or inside IoT appliances.
Simplified & Secure
K3s is packaged as a single <70MB binary that reduces the dependencies and steps needed to install, run and auto-update a production Kubernetes cluster.
Optimized for ARM
Both ARM64 and ARMv7 are supported with binaries and multiarch images available for both. K3s works great on something as small as a Raspberry Pi to an AWS a1.4xlarge 32GiB server.
How it Works
The above figure shows the difference between K3s server and K3s agent nodes. For more information, see the architecture documentation.
Get Started
1. Download K3s - latest release: x86_64, ARMv7, and ARM64 are supported
2. Run server
sudo k3s server &
# Kubeconfig is written to /etc/rancher/k3s/k3s.yaml
sudo k3s kubectl get node
# On a different node run the below command.
# NODE_TOKEN comes from /var/lib/rancher/k3s/server/node-token on your server
sudo k3s agent --server https://myserver:6443 --token ${NODE_TOKEN}



