mirror of
https://gitea.com/gitea/act_runner.git
synced 2026-10-28 19:06:02 +08:00
41f1e08bec
Renovate gets no release timestamps for Docker Hub images with more than 1000 tags (https://github.com/renovatebot/renovate/issues/46925) or for quay.io, so the 5-day minimum release age holds them back forever. The e2e workflows, the Kubernetes examples and the toolkit test pins are outside its managers, so these are bumped by hand. The builder follows the current Alpine instead of the frozen 3.23. Reviewed-on: https://gitea.com/gitea/runner/pulls/1330 Reviewed-by: bircni <bircni@icloud.com> Co-authored-by: silverwind <me@silverwind.io>
Kubernetes deployments of gitea-runner
Jobs can run on Kubernetes in two ways:
- Job pods: each job runs as its own pod, without privileged containers and under the cluster's quotas and policies. Docker actions and
docker://steps are not supported. Deploy withkubernetes-pods.yamland see docs/kubernetes.md. - Docker in Docker: jobs run in a Docker daemon next to the runner. Every workflow feature works, but the daemon is privileged, so a job can break out to the node. Deploy with
dind-docker.yaml,statefulset-dind.yamlfor several replicas,rootless-docker.yamlfor a rootless daemon, or the Helm chart. The sidecars in the first two need Kubernetes 1.29 or later.
All examples read the registration token from the runner-secret Secret and the Gitea URL from GITEA_INSTANCE_URL, and keep the registration in /data. They give a stopping pod three hours to finish its jobs, so keep runner.shutdown_timeout below terminationGracePeriodSeconds.