- 最新
- 投票最多
- 评论最多
Have you looked into this? https://docs.github.com/en/actions/using-github-hosted-runners/connecting-to-a-private-network. Seems the feasible approach is to use API Gateway with OIDC, thought your requirement may be stricter than that.
According to Communication between self hosted runners and GitHub Enterprise Cloud a long poll https connection and several other bidirectional https connections are required from the GitHub Runner to GitHub.
Given your architecture and constraints, it may be possible to set up a proxy service that can centralize the outbound network access needed. Information is available at using a proxy server with self-hosted runners.
In combination with the workflow_job web hook event, you may be able to automatically turn the proxy on and off in an as needed basis. More information at webhook events and payloads: workflow_job.
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 4 个月前
- AWS 官方已更新 1 年前