Date: 2026-02-07
Cluster: drg-k8s (context: kubernetes-admin@kubernetes)
Enabled Gitea Actions execution on drg-k8s by:
kube-proxy kubeconfig to point to the current control-plane IP (restored pod -> ClusterIP routing).gitea/act_runner) in Kubernetes with a Docker engine sidecar.Observed symptom:
http://gitea-http:3000).Root cause:
kube-system/configmap/kube-proxy had server: https://192.168.1.216:6443 (old control-plane IP).Action:
server: https://192.168.1.9:6443.daemonset/kube-proxy.Result:
gitea-http:3000 returned 200).Observed symptom:
chown/chmod ... Operation not permitted for /data/git, implying repo storage was not writable by the Gitea UID/GID (1240000012 / 1240000009).Action:
/mnt/bigdata/personal/projects/git/{repositories,lfs} to /mnt/fastdata/k8s-pvcs/gitea/git/{repositories,lfs}.deployment/gitea to mount /mnt/fastdata/k8s-pvcs/gitea/git as /data/git.2770 with group files-bigdata-rw so group members can access data via normal file services.Result:
Action:
configmap/gitea-act-runner-config and secret/gitea-act-runner-env (runner registration token stored only in Kubernetes Secret).deployment/gitea-act-runner with:
gitea/act_runner:0.2.13docker:27-dind sidecar running dockerd directly and exposing only a shared unix socket: unix:///run/docker/docker.sockResult:
action_runner table count became 1).Docker is ready and runner declares labels successfully.