A Forgejo Runner plugin that spawn jobs as Kubernetes pods
kubernetes ci forgejo runner

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 Commit Parent f7852de9
+36 -46
6 changed files
+36 -46
6 changed files