Skip to content

Latest commit

 

History

History
16 lines (10 loc) · 925 Bytes

README.md

File metadata and controls

16 lines (10 loc) · 925 Bytes

Why k3s?

It's lightweight, multiarch, supports high availability and works great on small production environments.

How it works:

  • A server node is defined as a host running the k3s server command, with control-plane and datastore components managed by K3s.
  • An agent node is defined as a host running the k3s agent command, without any datastore or control-plane components.
  • Both servers and agents run the kubelet, container runtime, and CNI. See the Advanced Options documentation for more information on running agentless servers.

Single-server Setup with an Embedded DB