mirror of
https://code.forgejo.org/forgejo/runner.git
synced 2025-06-27 16:35:58 +00:00
Hi! ~~ba2fc1273ce5cb04d96cfdbb47ebad929dcbd96f goes in tandem with https://code.forgejo.org/forgejo/act/pulls/135 and adapts to the API changes for `runner.Config.`~~ I dropped the act interface changes according to https://code.forgejo.org/forgejo/act/pulls/135#issuecomment-40695, but kept the CLI changes here - as they are not breaking here. Other three commits just fix up some typos around the tree - bit of a pet peeve of mine, sorry :^) Reviewed-on: https://code.forgejo.org/forgejo/runner/pulls/576 Reviewed-by: earl-warren <earl-warren@noreply.code.forgejo.org> Co-authored-by: Christoph Heiss <christoph@c8h4.io> Co-committed-by: Christoph Heiss <christoph@c8h4.io> |
||
---|---|---|
.. | ||
dind-docker.yaml | ||
README.md |
Kubernetes Docker in Docker Deployment
Registers Kubernetes pod runners using offline registration, allowing the scaling of runners as needed.
NOTE: Docker in Docker (dind) requires elevated privileges on Kubernetes. The current way to achieve this is to set the pod SecurityContext
to privileged
. Keep in mind that this is a potential security issue that has the potential for a malicious application to break out of the container context.
dind-docker.yaml
creates a deployment and secret for Kubernetes to act as a runner. The Docker credentials are re-generated each time the pod connects and does not need to be persisted.