boxctl
DocsSign in

k3s-fc

Deploys a K3s server instance on Firecracker microVMs (flannel host-gw backend, no VXLAN needed).

Use it on boxctl

  1. On the dashboard, pick k3s-fc in the Template picker and click Boot box.
  2. The box boots, then runs k3s-fc/k3s-server.sh on itself. The button reads Booting… until the script has finished.
  3. Open the box's Terminal and follow the guide below. The box's row keeps a link back to this page under the template's name.

The guide is shared with the onctl CLI, so it starts from an onctl up -a k3s-fc/k3s-server.sh command. Booting a box with this template replaces that command; everything the guide runs on the VM itself applies as written.

K3s server for Firecracker (and other VXLAN-less kernels)

onctl up -n qwe -a k3s-fc/k3s-server.sh --download /tmp/k3s.yaml

Identical to k3s/k3s-server.sh, except flannel's CNI backend is set to host-gw instead of the default vxlan. onctl's fc provider (Firecracker microVMs) doesn't support the VXLAN kernel module, which makes a plain k3s/k3s-server.sh install crash-loop (failed to create vxlan device: operation not supported). Use this template instead of k3s/k3s-server.sh when provisioning with -p fc.

kubectl --kubeconfig k3s.yaml get po -A

OR

export KUBECONFIG=$PWD/k3s.yaml

k3s server token is random generated by the server script, and can be found on /tmp/token.

See the template's source for exactly what it runs.