GitHub runner
- By Canonical IS DevOps
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 256 | 11 Sep 2024 | |
| latest/stable | 244 | 27 Aug 2024 | |
| latest/stable | 1 | 09 Feb 2022 | |
| latest/beta | 257 | 12 Sep 2024 | |
| latest/beta | 234 | 05 Aug 2024 | |
| latest/edge | 263 | Today | |
| latest/edge | 262 | 13 Sep 2024 | |
| latest/edge | 4 | 26 Apr 2022 | |
| 1/stable | 177 | 05 Jun 2024 | |
| 1/edge | 177 | 05 Jun 2024 |
juju deploy github-runner --channel 1/edge
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
22.04
20.04
How to restrict self-hosted runner network access
The denylist configuration can be used to restrict network access for self-hosted runners.
This can be employed to prevent self-hosted runners from accessing the network on the Juju machine. Generally, all IPv4 local addresses should be included in the denylist:
- 0.0.0.0/8
- 10.0.0.0/8
- 100.64.0.0/10
- 127.0.0.0/8
- 169.254.0.0/16
- 172.16.0.0/12
- 192.0.0.0/24
- 192.0.2.0/24
- 192.88.99.0/24
- 192.168.0.0/16
- 198.18.0.0/15
- 198.51.100.0/24
- 203.0.113.0/24
- 224.0.0.0/4
- 233.252.0.0/24
- 240.0.0.0/4
Additionally, include any IPv4 address or CIDR block that the runner should not have access to on the denylist.