Something went wrong. Try again.
A Forgejo Runner plugin that spawn jobs as Kubernetes pods
kubernetes ci forgejo runner
Something went wrong. Try again.
feat!: reject workflows defining service ports
This was previously accepted if and only if the host port and container port were identical. In retrospect, this doesn't actually make much sense in the case of Kubernetes, since the service is running as a sidecar container in the same pod as the job. This means they share their network and we would never need to actually expose ports from a service container on the host itself.
Author Date (Oct 8, 2026, 5:04 PM UTC) Commit
Copy SHA
Parent f7852de9 f7852de9305d6d5f2f6fa8a98e8705243e10e16b