You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/github/manage-github-actions-enterprise/includes/manage-runners.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ To configure IP allow lists for internal applications and systems to interact wi
54
54
#### 1. Understand GitHub's IP address ranges
55
55
GitHub-hosted runners operate within specific IP address ranges. To ensure your internal applications can communicate with these runners, you need to allow these IP ranges through your firewall. GitHub provides a meta API endpoint https://api.github.com/meta that lists all current IP address ranges used by GitHub services, including those for Actions runners. Regularly updating your allow lists based on this information is essential, as IP ranges can change.
56
56
57
-

57
+
:::image type="content" source="../media/github-runners-ip-ranges.png" alt-text="Screenshot of API response showing GitHub runners IP ranges.":::
58
58
59
59
#### 2. Configure your firewall
60
60
@@ -67,7 +67,7 @@ GitHub-hosted runners operate within specific IP address ranges. To ensure your
67
67
#### 3. Consider using self-hosted runners
68
68
If maintaining an IP allow list for GitHub-hosted runners is challenging due to frequent changes in IP ranges, consider setting up self-hosted runners within your network. This approach allows you to have more control over the runner environment and network configurations. However, be aware that using self-hosted runners requires additional maintenance and infrastructure management.
69
69
70
-

70
+
:::image type="content" source="../media/github-self-hosted-runners.png" alt-text="Screenshot of an empty runners screen.":::
71
71
72
72
#### 4. Regularly review and update allow lists
73
73
Since GitHub's IP address ranges can change, it's crucial to periodically review and update your firewall's IP allow lists. Automating this process by scripting the retrieval of IP ranges from GitHub's meta API can help ensure your allow lists remain current without manual intervention.
@@ -141,7 +141,7 @@ GitHub Actions supports two types of runners:
141
141
- Recommended for **private repositories, enterprise workloads, and performance-intensive tasks**.
142
142
143
143
144
-
#### Choosing Between GitHub-hosted and Self-hosted Runners
144
+
#### Choosing between GitHub-hosted and Self-hosted Runners
145
145
146
146
Two types of runners can execute GitHub Actions workflows: GitHub-hosted runners or self-hosted runners.
0 commit comments