Paid project · k3d / k3s

k3d / k3s: from one Docker host to several nodes

When lightweight Kubernetes is worth it, what gets delivered, when it is not, and how to pick between k3d and k3s.

When you need it

One Docker host is not enough: services need declarative deployment, Ingress, rolling updates and one place for monitoring, but a full Kubernetes setup is too much.

k3s is Kubernetes with fewer moving parts, suited to a small cluster of machines. k3d runs k3s inside Docker, which is a good way to practice the workflow on one machine first.

What gets delivered

  • Topology: how many servers and agents, or a single-node k3d.
  • Installation: k3s server and agent settings, basic networking and storage configuration.
  • Ingress: the built-in Traefik or your own, and how hostnames are wired.
  • Storage: local-path, NFS or whatever you already have, and which data belongs where.
  • Monitoring: node and pod metrics into Prometheus and Grafana.
  • A minimal working checklist: deploy a real service, roll an update, restart a machine and watch it recover.
  • A judgement on when k8s is the wrong answer, and how to go back.

Not included

  • Production-grade high availability. No multi-master failover for a home or small team.
  • Deep CNI tuning or network policy design.
  • The backup system itself; you get advice and the integration points.
  • Rewriting every Compose service into Kubernetes manifests.

Who it fits

Two or three machines, a growing set of services, and a willingness to learn basic Kubernetes. With one machine and a few containers, Docker Compose is less work.

How to start

Email how many machines, what runs on them, why k8s, and whether storage and backups exist. Scope first, then a quote.

Questions

k3d or k3s?

k3d to practice locally and validate manifests and Ingress; k3s to run on real machines long term.

Is it worth it on one machine?

Usually not. Compose is more direct on a single host, unless you are preparing for several nodes later.

Related

Email is the only channel. Questions, corrections or a scope request: [email protected]. This page also exists as Markdown: /services/k8s.md.

Not sure where to start?

Run the assessment first, or send your setup and goal by email. The reply says whether it fits and what happens next.