The Kubernetes lab we ran at Cloud Native Summit Kerala — and the installer you were meant to take home.
$ git clone https://lab.knownhost.com/cns-kerala-lab
Hosted on this machine, not on GitHub. If you would rather not use git: download the tarball.
$ curl -fsSL https://lab.knownhost.com/k3s | sudo bash -s -- --domain apps.example.com
About four minutes to a single-node Kubernetes with Traefik ingress, cert-manager wired to Let's Encrypt, a hardened host, and a sample app answering on real HTTPS.
Point that domain at the box first — the script checks, because Let's Encrypt cannot issue for a name that does not resolve. And read the script before you pipe it into a shell. It is served as plain text precisely so you can.
install/kh-k3s.sh — the installer above.lab/ — the three-fault puzzle, packaged for your own
cluster. One Deployment stuck at 0/2 Ready, three separate
causes, revealed one at a time. verify.sh grades it the same
way the booth did.killercoda/ — the same puzzle in a browser, if you have
no VPS to hand.It is a single KnownHost unmanaged VPS — 8 vCPU, 12 GB — running k3s. On the day it handed out one throwaway Kubernetes namespace per attendee, thirty at a time, and measured about 44 MB per session. The whole booth would have fitted on the $20/mo plan.