Files
OKF_CV_Website/decisions/freelens-admin-ui.md
T
Noel Sabia e022c30527 feat(okf): run on full Kubernetes with FreeLens for admin
k3s is out. The cluster is upstream Kubernetes installed with kubeadm:
containerd, single control-plane etcd, Calico for NetworkPolicy.

- add the cluster decision and the FreeLens decision
- move Terraform from the k3s service to kubeadm, Calico, metrics-server
  and the local-path provisioner
- budget ~900 MB for the control plane and plan a bigger machine before 0.3.0
- note kubelet failSwapOn and containerd hosts.toml
- rename 0.3.0 and commit the 0.2.0 done-when to the new stack
- update the German learning plan
2026-10-24 19:02:17 +02:00

1.9 KiB

type, title, description, tags, status, generated, verified
type title description tags status generated verified
Decision FreeLens as Noel's admin UI FreeLens runs on Noel's laptop and reaches the API through an SSH tunnel; visitors and agents never get cluster access.
decision
kubernetes
operations
freelens
stable
by at
opencode-go/deepseek-v4.1-flash 2026-10-24T00:00:00Z
by at
human:noel 2026-10-24T00:00:00Z

Decision

Noel inspects and debugs the cluster in FreeLens on his own laptop. The kubeconfig points at https://127.0.0.1:6443, and an SSH tunnel forwards that port to the control plane, which listens only on localhost.

Visitors and browser agents never receive a kubeconfig. The public site keeps using the gateway API.

Why

  • FreeLens gives pods, events, logs, probes and YAML without the project building its own dashboard.
  • The API server is not exposed to the internet: no port-forward on 6443, no public endpoint, no certificate dance beyond SSH.
  • The kubeconfig holds a client certificate. Leaving it on the laptop and tunnelling the port keeps the cluster off the public attack surface.
  • It closes the gap between "read-only gateway view" and "I need to see why a pod is CrashLooping".

Consequences

  • Admin work (delete a stuck pod, read kubelet logs, change a quota) happens in FreeLens or kubectl, never through the CV page.
  • The SSH tunnel is a manual step: ssh -L 6443:127.0.0.1:6443 server0, then open FreeLens. That is acceptable for a single admin.
  • The bundle's rule becomes "no visitor gets Kubernetes API access", not "nobody does". Noel is the only holder of a kubeconfig.
  • FreeLens is a new tool and needs approval under the stack rule; it is approved here because it replaces a self-built dashboard at zero server cost.

Details

Runtime boundaries: system. The developer view on the site (release 1.3.0) stays read-only through the gateway and is not a FreeLens replacement.