Snapshot date: 2026-02-07
Kubernetes control-plane node (also runs service workloads). Acts as the ingress endpoint for internal *.app.lan hostnames.
Placement verified 2026-09-15: the cluster also has the dedicated worker node drg-k8s-worker-01.auth.home.lan (192.168.1.231). AutoCoder Codex task execution and builds/tests belong there, including those initiated by direct administrator sessions. See AutoCoder worker placement. The remaining host facts below are the dated February snapshot, not a current inventory.
drg-k8s.auth.home.lan6.8.0-90-genericenp1s0192.168.1.9/24192.168.1.1drg-k8s.auth.home.lan (role: control-plane)v1.35.0containerd://1.7.28tunl0 and cali* present)Namespaces observed (non-exhaustive, snapshot):
autocoder-enginegiteaingress-nginxkubernetes-dashboardlocal-path-storageIngress controller:
ingress-nginxingress-nginx-controlleringress-nginx-controller (NodePort)
80:30331/TCP443:30402/TCPThese mounts are used for hostPath-based Kubernetes storage on this node:
/mnt/fastdata (NFSv4.2 from kryptovisor.auth.home.lan / 192.168.1.4)/mnt/bigdata (NFSv4.2 from kryptovisor.auth.home.lan / 192.168.1.4)See:
server-documentations/drg-k8s/storage/mnt-fastdata.mdserver-documentations/drg-k8s/storage/mnt-bigdata.md22/tcp: SSH to this node6443/tcp: Kubernetes API server (control-plane)222/tcp: reserved for Gitea SSH (hostPort; see server-documentations/drg-k8s/services/gitea/overview.md)