SEC.01

The playbook

The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.

1. 01reconk3s already installed? (then check the node and skip)
2. 02reconanother Kubernetes already running? (then stop)
3. 03reconCPU and RAM (k3s server: 2 cores and 2 GB minimum)
4. 04reconports 6443/10250 free? 80/443 already taken (then disable Traefik and ServiceLB)?
5. 05reconactive firewall (ufw or firewalld) to configure for the cluster networks
6. 06reconoverlap with k3s CIDRs (10.42.0.0/16 pods, 10.43.0.0/16 services)
7. 07reconcurrent default route (must be identical after the install)
8. 08actDownload the official installerverify
9. 09actAllow the cluster networks (only if ufw or firewalld is active)verify
10. 10actInstall k3sdestructiveverify
11. 11actThe node is Readyverify
12. 12actProtect the kubeconfigverify

SEC.02

What it verifies

Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.

1. 01verifyDownload the official installerVerified byhead -1 /tmp/k3s-install.sh
2. 02verifyAllow the cluster networks (only if ufw or firewalld is active)Verified byufw status 2>/dev/null | grep -c '10.4[23].0.0/16' || firewall-cmd --zone=trusted --list-sources
3. 03verifyInstall k3sVerified bysystemctl is-active k3s && ip -4 route show default
4. 04verifyThe node is ReadyVerified byk3s kubectl get nodes --no-headers | grep -c " Ready"
5. 05verifyProtect the kubeconfigVerified bystat -c %a /etc/rancher/k3s/k3s.yaml

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

SEC.04

How a recipe runs in Servor

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.

SEC.05

Deploy on Servor button

Maintain k3s (lightweight Kubernetes) or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.

SEC.06

More containers recipes

1. 01Docker EngineDocker Engine + Compose from the official repository, service active, hello-world verified.
2. 02Docker ComposeDocker Compose plugin (docker compose), installed and verified.
3. 03PodmanPodman (daemonless containers, rootless capable), verified.
4. 04PortainerPortainer CE (LTS) Docker management web UI, admin preconfigured.
5. 05WatchtowerAutomatic, scheduled updates for Docker containers.